'\" t
.\" Man page generated from reStructuredText.
.
.
.nr rst2man-indent-level 0
.
.de1 rstReportMargin
\\$1 \\n[an-margin]
level \\n[rst2man-indent-level]
level margin: \\n[rst2man-indent\\n[rst2man-indent-level]]
-
\\n[rst2man-indent0]
\\n[rst2man-indent1]
\\n[rst2man-indent2]
..
.de1 INDENT
.\" .rstReportMargin pre:
. RS \\$1
. nr rst2man-indent\\n[rst2man-indent-level] \\n[an-margin]
. nr rst2man-indent-level +1
.\" .rstReportMargin post:
..
.de UNINDENT
. RE
.\" indent \\n[an-margin]
.\" old: \\n[rst2man-indent\\n[rst2man-indent-level]]
.nr rst2man-indent-level -1
.\" new: \\n[rst2man-indent\\n[rst2man-indent-level]]
.in \\n[rst2man-indent\\n[rst2man-indent-level]]u
..
.TH "CMAKE-PROPERTIES" "7" "Aug 27, 2025" "4.1.1" "CMake"
.SH NAME
cmake-properties \- CMake Properties Reference
.SH PROPERTIES OF GLOBAL SCOPE
.SS ALLOW_DUPLICATE_CUSTOM_TARGETS
.sp
Allow duplicate custom targets to be created.
.sp
Normally CMake requires that all targets built in a project have
globally unique logical names (see policy \fI\%CMP0002\fP).
This is necessary to generate meaningful project file names in
\fI\%Xcode\fP and \fI\%Visual Studio Generators\fP IDE
generators.  It also allows the target names to be referenced
unambiguously.
.sp
Makefile generators are capable of supporting duplicate \fI\%add_custom_target()\fP
names.  For projects that care only about \fI\%Makefile Generators\fP and do
not wish to support \fI\%Xcode\fP or \fI\%Visual Studio Generators\fP IDE
generators, one may set this property to \fBTrue\fP
to allow duplicate custom targets.  The property
allows multiple \fI\%add_custom_target()\fP command calls in different
directories to specify the same target name.  However, setting this
property will cause non\-Makefile generators to produce an error and
refuse to generate the project.
.SS AUTOGEN_SOURCE_GROUP
.sp
Added in version 3.9.

.sp
Name of the  \fI\%source_group()\fP for \fI\%AUTOMOC\fP,
\fI\%AUTORCC\fP and \fI\%AUTOUIC\fP generated files.
.sp
Files generated by \fI\%AUTOMOC\fP, \fI\%AUTORCC\fP and
\fI\%AUTOUIC\fP are not always known at configure time and therefore can\(aqt
be passed to \fI\%source_group()\fP\&.
\fBAUTOGEN_SOURCE_GROUP\fP can be used instead to generate or select
a source group for \fI\%AUTOMOC\fP, \fI\%AUTORCC\fP and
\fI\%AUTOUIC\fP generated files.
.sp
For \fI\%AUTOMOC\fP, \fI\%AUTORCC\fP and \fI\%AUTOUIC\fP specific
overrides see \fI\%AUTOMOC_SOURCE_GROUP\fP, \fI\%AUTORCC_SOURCE_GROUP\fP
and \fI\%AUTOUIC_SOURCE_GROUP\fP respectively.
.SS AUTOGEN_TARGETS_FOLDER
.sp
Name of \fI\%FOLDER\fP for \fB*_autogen\fP targets that are added
automatically by CMake for targets for which \fI\%AUTOMOC\fP is enabled.
.sp
If not set, CMake uses the \fI\%FOLDER\fP property of the parent target as a
default value for this property.  See also the documentation for the
\fI\%FOLDER\fP target property and the \fI\%AUTOMOC\fP target property.
.SS AUTOMOC_SOURCE_GROUP
.sp
Added in version 3.9.

.sp
Name of the  \fI\%source_group()\fP for \fI\%AUTOMOC\fP generated files.
.sp
When set this is used instead of \fI\%AUTOGEN_SOURCE_GROUP\fP for
files generated by \fI\%AUTOMOC\fP\&.
.SS AUTOMOC_TARGETS_FOLDER
.sp
Name of \fI\%FOLDER\fP for \fB*_autogen\fP targets that are added automatically by
CMake for targets for which \fI\%AUTOMOC\fP is enabled.
.sp
This property is obsolete.  Use \fI\%AUTOGEN_TARGETS_FOLDER\fP instead.
.sp
If not set, CMake uses the \fI\%FOLDER\fP property of the parent target as a
default value for this property.  See also the documentation for the
\fI\%FOLDER\fP target property and the \fI\%AUTOMOC\fP target property.
.SS AUTORCC_SOURCE_GROUP
.sp
Added in version 3.9.

.sp
Name of the  \fI\%source_group()\fP for \fI\%AUTORCC\fP generated files.
.sp
When set this is used instead of \fI\%AUTOGEN_SOURCE_GROUP\fP for
files generated by \fI\%AUTORCC\fP\&.
.SS AUTOUIC_SOURCE_GROUP
.sp
Added in version 3.21.

.sp
Name of the  \fI\%source_group()\fP for \fI\%AUTOUIC\fP generated files.
.sp
When set this is used instead of \fI\%AUTOGEN_SOURCE_GROUP\fP for
files generated by \fI\%AUTOUIC\fP\&.
.SS CMAKE_C_KNOWN_FEATURES
.sp
Added in version 3.1.

.sp
List of C features known to this version of CMake.
.sp
The features listed in this global property may be known to be available to the
C compiler.  If the feature is available with the C compiler, it will
be listed in the \fI\%CMAKE_C_COMPILE_FEATURES\fP variable.
.sp
The features listed here may be used with the \fI\%target_compile_features()\fP
command.  See the \fI\%cmake\-compile\-features(7)\fP manual for information on
compile features and a list of supported compilers.
.sp
The features known to this version of CMake are listed below.
.SS High level meta features indicating C standard support
.sp
Added in version 3.8.

.INDENT 0.0
.TP
.B \fBc_std_90\fP
Compiler mode is at least C 90.
.TP
.B \fBc_std_99\fP
Compiler mode is at least C 99.
.TP
.B \fBc_std_11\fP
Compiler mode is at least C 11.
.TP
.B \fBc_std_17\fP
Added in version 3.21.

.sp
Compiler mode is at least C 17.
.TP
.B \fBc_std_23\fP
Added in version 3.21.

.sp
Compiler mode is at least C 23.
.UNINDENT
.sp
\fBNOTE:\fP
.INDENT 0.0
.INDENT 3.5
If the compiler\(aqs default standard level is at least that
of the requested feature, CMake may omit the \fB\-std=\fP flag.
The flag may still be added if the compiler\(aqs default extensions mode
does not match the \fI\%<LANG>_EXTENSIONS\fP target property,
or if the \fI\%<LANG>_STANDARD\fP target property is set.
.UNINDENT
.UNINDENT
.SS Low level individual compile features
.INDENT 0.0
.TP
.B \fBc_function_prototypes\fP
Function prototypes, as defined in \fBISO/IEC 9899:1990\fP\&.
.TP
.B \fBc_restrict\fP
\fBrestrict\fP keyword, as defined in \fBISO/IEC 9899:1999\fP\&.
.TP
.B \fBc_static_assert\fP
Static assert, as defined in \fBISO/IEC 9899:2011\fP\&.
.TP
.B \fBc_variadic_macros\fP
Variadic macros, as defined in \fBISO/IEC 9899:1999\fP\&.
.UNINDENT
.SS CMAKE_CUDA_KNOWN_FEATURES
.sp
Added in version 3.17.

.sp
List of CUDA features known to this version of CMake.
.sp
The features listed in this global property may be known to be available to the
CUDA compiler.  If the feature is available with the C++ compiler, it will
be listed in the \fI\%CMAKE_CUDA_COMPILE_FEATURES\fP variable.
.sp
The features listed here may be used with the \fI\%target_compile_features()\fP
command.  See the \fI\%cmake\-compile\-features(7)\fP manual for information on
compile features and a list of supported compilers.
.sp
The features known to this version of CMake are:
.INDENT 0.0
.TP
.B \fBcuda_std_03\fP
Compiler mode is at least CUDA/C++ 03.
.TP
.B \fBcuda_std_11\fP
Compiler mode is at least CUDA/C++ 11.
.TP
.B \fBcuda_std_14\fP
Compiler mode is at least CUDA/C++ 14.
.TP
.B \fBcuda_std_17\fP
Compiler mode is at least CUDA/C++ 17.
.TP
.B \fBcuda_std_20\fP
Compiler mode is at least CUDA/C++ 20.
.TP
.B \fBcuda_std_23\fP
Added in version 3.20.

.sp
Compiler mode is at least CUDA/C++ 23.
.TP
.B \fBcuda_std_26\fP
Added in version 3.30.

.sp
Compiler mode is at least CUDA/C++ 26.
.UNINDENT
.sp
\fBNOTE:\fP
.INDENT 0.0
.INDENT 3.5
If the compiler\(aqs default standard level is at least that
of the requested feature, CMake may omit the \fB\-std=\fP flag.
The flag may still be added if the compiler\(aqs default extensions mode
does not match the \fI\%<LANG>_EXTENSIONS\fP target property,
or if the \fI\%<LANG>_STANDARD\fP target property is set.
.UNINDENT
.UNINDENT
.SS CMAKE_CXX_KNOWN_FEATURES
.sp
Added in version 3.1.

.sp
List of C++ features known to this version of CMake.
.sp
The features listed in this global property may be known to be available to the
C++ compiler.  If the feature is available with the C++ compiler, it will
be listed in the \fI\%CMAKE_CXX_COMPILE_FEATURES\fP variable.
.sp
The features listed here may be used with the \fI\%target_compile_features()\fP
command.  See the \fI\%cmake\-compile\-features(7)\fP manual for information on
compile features and a list of supported compilers.
.sp
The features known to this version of CMake are listed below.
.SS High level meta features indicating C++ standard support
.sp
Added in version 3.8.

.sp
The following meta features indicate general support for the associated
language standard.  It reflects the language support claimed by the compiler,
but it does not necessarily imply complete conformance to that standard.
.INDENT 0.0
.TP
.B \fBcxx_std_98\fP
Compiler mode is at least C++ 98.
.TP
.B \fBcxx_std_11\fP
Compiler mode is at least C++ 11.
.TP
.B \fBcxx_std_14\fP
Compiler mode is at least C++ 14.
.TP
.B \fBcxx_std_17\fP
Compiler mode is at least C++ 17.
.TP
.B \fBcxx_std_20\fP
Added in version 3.12.

.sp
Compiler mode is at least C++ 20.
.TP
.B \fBcxx_std_23\fP
Added in version 3.20.

.sp
Compiler mode is at least C++ 23.
.TP
.B \fBcxx_std_26\fP
Added in version 3.30.

.sp
Compiler mode is at least C++ 26.
.UNINDENT
.sp
\fBNOTE:\fP
.INDENT 0.0
.INDENT 3.5
If the compiler\(aqs default standard level is at least that
of the requested feature, CMake may omit the \fB\-std=\fP flag.
The flag may still be added if the compiler\(aqs default extensions mode
does not match the \fI\%<LANG>_EXTENSIONS\fP target property,
or if the \fI\%<LANG>_STANDARD\fP target property is set.
.UNINDENT
.UNINDENT
.SS Low level individual compile features
.sp
For C++ 11 and C++ 14, compilers were sometimes slow to implement certain
language features.  CMake provided some individual compile features to help
projects determine whether specific features were available.  These individual
features are now less relevant and projects should generally prefer to use the
high level meta features instead.  Individual compile features are not provided
for C++ 17 or later.
.sp
See the \fI\%cmake\-compile\-features(7)\fP manual for further discussion of
the use of individual compile features.
.SS Individual features from C++ 98
.INDENT 0.0
.TP
.B \fBcxx_template_template_parameters\fP
Template template parameters, as defined in \fBISO/IEC 14882:1998\fP\&.
.UNINDENT
.SS Individual features from C++ 11
.INDENT 0.0
.TP
.B \fBcxx_alias_templates\fP
Template aliases, as defined in \X'tty: link https://www.open-std.org/jtc1/sc22/wg21/docs/papers/2007/n2258.pdf'\fI\%N2258\fP\X'tty: link'\&.
.TP
.B \fBcxx_alignas\fP
Alignment control \fBalignas\fP, as defined in \X'tty: link https://www.open-std.org/jtc1/sc22/wg21/docs/papers/2007/n2341.pdf'\fI\%N2341\fP\X'tty: link'\&.
.TP
.B \fBcxx_alignof\fP
Alignment control \fBalignof\fP, as defined in \X'tty: link https://www.open-std.org/jtc1/sc22/wg21/docs/papers/2007/n2341.pdf'\fI\%N2341\fP\X'tty: link'\&.
.TP
.B \fBcxx_attributes\fP
Generic attributes, as defined in \X'tty: link https://www.open-std.org/jtc1/sc22/wg21/docs/papers/2008/n2761.pdf'\fI\%N2761\fP\X'tty: link'\&.
.TP
.B \fBcxx_auto_type\fP
Automatic type deduction, as defined in \X'tty: link https://www.open-std.org/jtc1/sc22/wg21/docs/papers/2006/n1984.pdf'\fI\%N1984\fP\X'tty: link'\&.
.TP
.B \fBcxx_constexpr\fP
Constant expressions, as defined in \X'tty: link https://www.open-std.org/jtc1/sc22/wg21/docs/papers/2007/n2235.pdf'\fI\%N2235\fP\X'tty: link'\&.
.TP
.B \fBcxx_decltype_incomplete_return_types\fP
Decltype on incomplete return types, as defined in \X'tty: link https://www.open-std.org/jtc1/sc22/wg21/docs/papers/2011/n3276.pdf'\fI\%N3276\fP\X'tty: link'\&.
.TP
.B \fBcxx_decltype\fP
Decltype, as defined in \X'tty: link https://www.open-std.org/jtc1/sc22/wg21/docs/papers/2007/n2343.pdf'\fI\%N2343\fP\X'tty: link'\&.
.TP
.B \fBcxx_default_function_template_args\fP
Default template arguments for function templates, as defined in \X'tty: link https://www.open-std.org/jtc1/sc22/wg21/docs/cwg_defects.html#226'\fI\%DR226\fP\X'tty: link'
.TP
.B \fBcxx_defaulted_functions\fP
Defaulted functions, as defined in \X'tty: link https://www.open-std.org/jtc1/sc22/wg21/docs/papers/2007/n2346.htm'\fI\%N2346\fP\X'tty: link'\&.
.TP
.B \fBcxx_defaulted_move_initializers\fP
Defaulted move initializers, as defined in \X'tty: link https://www.open-std.org/jtc1/sc22/wg21/docs/papers/2010/n3053.html'\fI\%N3053\fP\X'tty: link'\&.
.TP
.B \fBcxx_delegating_constructors\fP
Delegating constructors, as defined in \X'tty: link https://www.open-std.org/jtc1/sc22/wg21/docs/papers/2006/n1986.pdf'\fI\%N1986\fP\X'tty: link'\&.
.TP
.B \fBcxx_deleted_functions\fP
Deleted functions, as defined in \X'tty: link https://www.open-std.org/jtc1/sc22/wg21/docs/papers/2007/n2346.htm'\fI\%N2346\fP\X'tty: link'\&.
.TP
.B \fBcxx_enum_forward_declarations\fP
Enum forward declarations, as defined in \X'tty: link https://www.open-std.org/jtc1/sc22/wg21/docs/papers/2008/n2764.pdf'\fI\%N2764\fP\X'tty: link'\&.
.TP
.B \fBcxx_explicit_conversions\fP
Explicit conversion operators, as defined in \X'tty: link https://www.open-std.org/jtc1/sc22/wg21/docs/papers/2007/n2437.pdf'\fI\%N2437\fP\X'tty: link'\&.
.TP
.B \fBcxx_extended_friend_declarations\fP
Extended friend declarations, as defined in \X'tty: link https://www.open-std.org/jtc1/sc22/wg21/docs/papers/2005/n1791.pdf'\fI\%N1791\fP\X'tty: link'\&.
.TP
.B \fBcxx_extern_templates\fP
Extern templates, as defined in \X'tty: link https://www.open-std.org/jtc1/sc22/wg21/docs/papers/2006/n1987.htm'\fI\%N1987\fP\X'tty: link'\&.
.TP
.B \fBcxx_final\fP
Override control \fBfinal\fP keyword, as defined in \X'tty: link https://www.open-std.org/JTC1/SC22/WG21/docs/papers/2009/n2928.htm'\fI\%N2928\fP\X'tty: link', \X'tty: link https://www.open-std.org/jtc1/sc22/wg21/docs/papers/2010/n3206.htm'\fI\%N3206\fP\X'tty: link' and \X'tty: link https://www.open-std.org/jtc1/sc22/wg21/docs/papers/2011/n3272.htm'\fI\%N3272\fP\X'tty: link'\&.
.TP
.B \fBcxx_func_identifier\fP
Predefined \fB__func__\fP identifier, as defined in \X'tty: link https://www.open-std.org/jtc1/sc22/wg21/docs/papers/2007/n2340.htm'\fI\%N2340\fP\X'tty: link'\&.
.TP
.B \fBcxx_generalized_initializers\fP
Initializer lists, as defined in \X'tty: link https://www.open-std.org/jtc1/sc22/wg21/docs/papers/2008/n2672.htm'\fI\%N2672\fP\X'tty: link'\&.
.TP
.B \fBcxx_inheriting_constructors\fP
Inheriting constructors, as defined in \X'tty: link https://www.open-std.org/jtc1/sc22/wg21/docs/papers/2008/n2540.htm'\fI\%N2540\fP\X'tty: link'\&.
.TP
.B \fBcxx_inline_namespaces\fP
Inline namespaces, as defined in \X'tty: link https://www.open-std.org/jtc1/sc22/wg21/docs/papers/2008/n2535.htm'\fI\%N2535\fP\X'tty: link'\&.
.TP
.B \fBcxx_lambdas\fP
Lambda functions, as defined in \X'tty: link https://www.open-std.org/jtc1/sc22/wg21/docs/papers/2009/n2927.pdf'\fI\%N2927\fP\X'tty: link'\&.
.TP
.B \fBcxx_local_type_template_args\fP
Local and unnamed types as template arguments, as defined in \X'tty: link https://www.open-std.org/jtc1/sc22/wg21/docs/papers/2008/n2657.htm'\fI\%N2657\fP\X'tty: link'\&.
.TP
.B \fBcxx_long_long_type\fP
\fBlong long\fP type, as defined in \X'tty: link https://www.open-std.org/jtc1/sc22/wg21/docs/papers/2005/n1811.pdf'\fI\%N1811\fP\X'tty: link'\&.
.TP
.B \fBcxx_noexcept\fP
Exception specifications, as defined in \X'tty: link https://www.open-std.org/jtc1/sc22/wg21/docs/papers/2010/n3050.html'\fI\%N3050\fP\X'tty: link'\&.
.TP
.B \fBcxx_nonstatic_member_init\fP
Non\-static data member initialization, as defined in \X'tty: link https://www.open-std.org/jtc1/sc22/wg21/docs/papers/2008/n2756.htm'\fI\%N2756\fP\X'tty: link'\&.
.TP
.B \fBcxx_nullptr\fP
Null pointer, as defined in \X'tty: link https://www.open-std.org/jtc1/sc22/wg21/docs/papers/2007/n2431.pdf'\fI\%N2431\fP\X'tty: link'\&.
.TP
.B \fBcxx_override\fP
Override control \fBoverride\fP keyword, as defined in \X'tty: link https://www.open-std.org/JTC1/SC22/WG21/docs/papers/2009/n2928.htm'\fI\%N2928\fP\X'tty: link', \X'tty: link https://www.open-std.org/jtc1/sc22/wg21/docs/papers/2010/n3206.htm'\fI\%N3206\fP\X'tty: link'
and \X'tty: link https://www.open-std.org/jtc1/sc22/wg21/docs/papers/2011/n3272.htm'\fI\%N3272\fP\X'tty: link'\&.
.TP
.B \fBcxx_range_for\fP
Range\-based for, as defined in \X'tty: link https://www.open-std.org/jtc1/sc22/wg21/docs/papers/2009/n2930.html'\fI\%N2930\fP\X'tty: link'\&.
.TP
.B \fBcxx_raw_string_literals\fP
Raw string literals, as defined in \X'tty: link https://www.open-std.org/jtc1/sc22/wg21/docs/papers/2007/n2442.htm'\fI\%N2442\fP\X'tty: link'\&.
.TP
.B \fBcxx_reference_qualified_functions\fP
Reference qualified functions, as defined in \X'tty: link https://www.open-std.org/jtc1/sc22/wg21/docs/papers/2007/n2439.htm'\fI\%N2439\fP\X'tty: link'\&.
.TP
.B \fBcxx_right_angle_brackets\fP
Right angle bracket parsing, as defined in \X'tty: link https://www.open-std.org/jtc1/sc22/wg21/docs/papers/2005/n1757.html'\fI\%N1757\fP\X'tty: link'\&.
.TP
.B \fBcxx_rvalue_references\fP
R\-value references, as defined in \X'tty: link https://www.open-std.org/jtc1/sc22/wg21/docs/papers/2006/n2118.html'\fI\%N2118\fP\X'tty: link'\&.
.TP
.B \fBcxx_sizeof_member\fP
Size of non\-static data members, as defined in \X'tty: link https://www.open-std.org/jtc1/sc22/wg21/docs/papers/2007/n2253.html'\fI\%N2253\fP\X'tty: link'\&.
.TP
.B \fBcxx_static_assert\fP
Static assert, as defined in \X'tty: link https://www.open-std.org/jtc1/sc22/wg21/docs/papers/2004/n1720.html'\fI\%N1720\fP\X'tty: link'\&.
.TP
.B \fBcxx_strong_enums\fP
Strongly typed enums, as defined in \X'tty: link https://www.open-std.org/jtc1/sc22/wg21/docs/papers/2007/n2347.pdf'\fI\%N2347\fP\X'tty: link'\&.
.TP
.B \fBcxx_thread_local\fP
Thread\-local variables, as defined in \X'tty: link https://www.open-std.org/jtc1/sc22/wg21/docs/papers/2008/n2659.htm'\fI\%N2659\fP\X'tty: link'\&.
.TP
.B \fBcxx_trailing_return_types\fP
Automatic function return type, as defined in \X'tty: link https://www.open-std.org/jtc1/sc22/wg21/docs/papers/2008/n2541.htm'\fI\%N2541\fP\X'tty: link'\&.
.TP
.B \fBcxx_unicode_literals\fP
Unicode string literals, as defined in \X'tty: link https://www.open-std.org/jtc1/sc22/wg21/docs/papers/2007/n2442.htm'\fI\%N2442\fP\X'tty: link'\&.
.TP
.B \fBcxx_uniform_initialization\fP
Uniform initialization, as defined in \X'tty: link https://www.open-std.org/jtc1/sc22/wg21/docs/papers/2008/n2640.pdf'\fI\%N2640\fP\X'tty: link'\&.
.TP
.B \fBcxx_unrestricted_unions\fP
Unrestricted unions, as defined in \X'tty: link https://www.open-std.org/jtc1/sc22/wg21/docs/papers/2008/n2544.pdf'\fI\%N2544\fP\X'tty: link'\&.
.TP
.B \fBcxx_user_literals\fP
User\-defined literals, as defined in \X'tty: link https://www.open-std.org/jtc1/sc22/wg21/docs/papers/2008/n2765.pdf'\fI\%N2765\fP\X'tty: link'\&.
.TP
.B \fBcxx_variadic_macros\fP
Variadic macros, as defined in \X'tty: link https://www.open-std.org/jtc1/sc22/wg21/docs/papers/2004/n1653.htm'\fI\%N1653\fP\X'tty: link'\&.
.TP
.B \fBcxx_variadic_templates\fP
Variadic templates, as defined in \X'tty: link https://www.open-std.org/jtc1/sc22/wg21/docs/papers/2007/n2242.pdf'\fI\%N2242\fP\X'tty: link'\&.
.UNINDENT
.SS Individual features from C++ 14
.INDENT 0.0
.TP
.B \fBcxx_aggregate_default_initializers\fP
Aggregate default initializers, as defined in \X'tty: link https://www.open-std.org/jtc1/sc22/wg21/docs/papers/2013/n3605.html'\fI\%N3605\fP\X'tty: link'\&.
.TP
.B \fBcxx_attribute_deprecated\fP
\fB[[deprecated]]\fP attribute, as defined in \X'tty: link https://www.open-std.org/jtc1/sc22/wg21/docs/papers/2013/n3760.html'\fI\%N3760\fP\X'tty: link'\&.
.TP
.B \fBcxx_binary_literals\fP
Binary literals, as defined in \X'tty: link https://www.open-std.org/jtc1/sc22/wg21/docs/papers/2012/n3472.pdf'\fI\%N3472\fP\X'tty: link'\&.
.TP
.B \fBcxx_contextual_conversions\fP
Contextual conversions, as defined in \X'tty: link https://www.open-std.org/jtc1/sc22/wg21/docs/papers/2012/n3323.pdf'\fI\%N3323\fP\X'tty: link'\&.
.TP
.B \fBcxx_decltype_auto\fP
\fBdecltype(auto)\fP semantics, as defined in \X'tty: link https://www.open-std.org/jtc1/sc22/wg21/docs/papers/2013/n3638.html'\fI\%N3638\fP\X'tty: link'\&.
.TP
.B \fBcxx_digit_separators\fP
Digit separators, as defined in \X'tty: link https://www.open-std.org/jtc1/sc22/wg21/docs/papers/2013/n3781.pdf'\fI\%N3781\fP\X'tty: link'\&.
.TP
.B \fBcxx_generic_lambdas\fP
Generic lambdas, as defined in \X'tty: link https://www.open-std.org/jtc1/sc22/wg21/docs/papers/2013/n3649.html'\fI\%N3649\fP\X'tty: link'\&.
.TP
.B \fBcxx_lambda_init_captures\fP
Initialized lambda captures, as defined in \X'tty: link https://www.open-std.org/jtc1/sc22/wg21/docs/papers/2013/n3648.html'\fI\%N3648\fP\X'tty: link'\&.
.TP
.B \fBcxx_relaxed_constexpr\fP
Relaxed constexpr, as defined in \X'tty: link https://www.open-std.org/jtc1/sc22/wg21/docs/papers/2013/n3652.html'\fI\%N3652\fP\X'tty: link'\&.
.TP
.B \fBcxx_return_type_deduction\fP
Return type deduction on normal functions, as defined in \X'tty: link https://www.open-std.org/jtc1/sc22/wg21/docs/papers/2012/n3386.html'\fI\%N3386\fP\X'tty: link'\&.
.TP
.B \fBcxx_variable_templates\fP
Variable templates, as defined in \X'tty: link https://www.open-std.org/jtc1/sc22/wg21/docs/papers/2013/n3651.pdf'\fI\%N3651\fP\X'tty: link'\&.
.UNINDENT
.SS CMAKE_HIP_KNOWN_FEATURES
.sp
Added in version 3.30.

.sp
List of HIP features known to this version of CMake.
.sp
The features listed in this global property may be known to be available to the
HIP compiler.  If the feature is available with the HIP compiler, it will
be listed in the \fI\%CMAKE_HIP_COMPILE_FEATURES\fP variable.
.sp
The features listed here may be used with the \fI\%target_compile_features()\fP
command.  See the \fI\%cmake\-compile\-features(7)\fP manual for information on
compile features and a list of supported compilers.
.sp
The features known to this version of CMake are:
.INDENT 0.0
.TP
.B \fBhip_std_98\fP
Compiler mode is at least HIP/C++ 98.
.TP
.B \fBhip_std_11\fP
Compiler mode is at least HIP/C++ 11.
.TP
.B \fBhip_std_14\fP
Compiler mode is at least HIP/C++ 14.
.TP
.B \fBhip_std_17\fP
Compiler mode is at least HIP/C++ 17.
.TP
.B \fBhip_std_20\fP
Compiler mode is at least HIP/C++ 20.
.TP
.B \fBhip_std_23\fP
Compiler mode is at least HIP/C++ 23.
.TP
.B \fBhip_std_26\fP
Added in version 3.30.

.sp
Compiler mode is at least HIP/C++ 26.
.UNINDENT
.sp
\fBNOTE:\fP
.INDENT 0.0
.INDENT 3.5
If the compiler\(aqs default standard level is at least that
of the requested feature, CMake may omit the \fB\-std=\fP flag.
The flag may still be added if the compiler\(aqs default extensions mode
does not match the \fI\%<LANG>_EXTENSIONS\fP target property,
or if the \fI\%<LANG>_STANDARD\fP target property is set.
.UNINDENT
.UNINDENT
.SS CMAKE_ROLE
.sp
Added in version 3.14.

.sp
Tells what mode the current running script is in. Could be one of several
values:
.INDENT 0.0
.TP
.B \fBPROJECT\fP
Running in project mode (processing a \fBCMakeLists.txt\fP file).
.TP
.B \fBSCRIPT\fP
Running in \fI\%cmake \-P\fP script mode.
.TP
.B \fBFIND_PACKAGE\fP
Running in \fI\%cmake \-\-find\-package\fP mode.
.TP
.B \fBCTEST\fP
Running in CTest script mode.
.TP
.B \fBCPACK\fP
Running in CPack.
.UNINDENT
.SS See Also
.INDENT 0.0
.IP \(bu 2
The \fI\%CMAKE_SCRIPT_MODE_FILE\fP variable.
.UNINDENT
.SS DEBUG_CONFIGURATIONS
.sp
This property specifies which \fI\%Build Configurations\fP are for debugging.
.sp
The value must be a \fI\%semicolon\-separated list\fP of
build configuration names.
Currently this property is used only by the \fI\%target_link_libraries()\fP
command.  Additional uses may be defined in the future.
.sp
This property must be set at the top level of the project and before
the first \fI\%target_link_libraries()\fP command invocation.  If any entry in
the list does not match a valid configuration for the project, the
behavior is undefined.
.sp
By default, this property is \fBnot set\fP\&.
.SS Examples
.sp
The following example adds a custom configuration to non\-optimized debug
configurations while preserving any existing ones.  If the project uses the
default \fBDebug\fP configuration, it should be included as well.
.INDENT 0.0
.INDENT 3.5
.sp
.EX
set_property(GLOBAL APPEND PROPERTY DEBUG_CONFIGURATIONS Debug CustomBuild)
.EE
.UNINDENT
.UNINDENT
.SS See Also
.INDENT 0.0
.IP \(bu 2
The \fI\%MAP_IMPORTED_CONFIG_<CONFIG>\fP target property, which maps build
configurations when linking to \fI\%Imported Targets\fP that have the
\fI\%IMPORTED_CONFIGURATIONS\fP property set.
.UNINDENT
.SS DISABLED_FEATURES
.sp
List of features which are disabled during the CMake run.
.sp
List of features which are disabled during the CMake run.  By default
it contains the names of all packages which were not found.  This is
determined using the \fB<NAME>_FOUND\fP variables.  Packages which are
searched \fBQUIET\fP are not listed.  A project can add its own features to
this list.  This property is used by the macros in
\fI\%FeatureSummary\fP module.
.SS ECLIPSE_EXTRA_CPROJECT_CONTENTS
.sp
Added in version 3.12.

.sp
Additional contents to be inserted into the generated Eclipse cproject file.
.sp
The cproject file defines the CDT specific information. Some third party IDE\(aqs
are based on Eclipse with the addition of other information specific to that IDE.
Through this property, it is possible to add this additional contents to
the generated project.
It is expected to contain valid XML.
.sp
Also see the \fI\%ECLIPSE_EXTRA_NATURES\fP property.
.SS ECLIPSE_EXTRA_NATURES
.sp
List of natures to add to the generated Eclipse project file.
.sp
Eclipse projects specify language plugins by using natures. This property
should be set to the unique identifier for a nature (which looks like a Java
package name).
.sp
Also see the \fI\%ECLIPSE_EXTRA_CPROJECT_CONTENTS\fP property.
.SS ENABLED_FEATURES
.sp
List of features which are enabled during the CMake run.
.sp
List of features which are enabled during the CMake run.  By default
it contains the names of all packages which were found.  This is
determined using the \fB<NAME>_FOUND\fP variables.  Packages which are
searched \fBQUIET\fP are not listed.  A project can add its own features to
this list.  This property is used by the macros in
\fI\%FeatureSummary\fP module.
.SS ENABLED_LANGUAGES
.sp
Read\-only property that contains the list of currently enabled languages
.sp
Set to list of currently enabled languages.
.SS FIND_LIBRARY_USE_LIB32_PATHS
.sp
Added in version 3.7.

.sp
Whether the \fI\%find_library()\fP command should automatically search
\fBlib32\fP directories.
.sp
\fBFIND_LIBRARY_USE_LIB32_PATHS\fP is a boolean specifying whether the
\fI\%find_library()\fP command should automatically search the \fBlib32\fP
variant of directories called \fBlib\fP in the search path when building 32\-bit
binaries.
.sp
See also the \fI\%CMAKE_FIND_LIBRARY_CUSTOM_LIB_SUFFIX\fP variable.
.SS FIND_LIBRARY_USE_LIB64_PATHS
.sp
Whether \fI\%find_library()\fP should automatically search lib64
directories.
.sp
FIND_LIBRARY_USE_LIB64_PATHS is a boolean specifying whether the
\fI\%find_library()\fP command should automatically search the lib64
variant of directories called lib in the search path when building
64\-bit binaries.
.sp
See also the \fI\%CMAKE_FIND_LIBRARY_CUSTOM_LIB_SUFFIX\fP variable.
.SS FIND_LIBRARY_USE_LIBX32_PATHS
.sp
Added in version 3.9.

.sp
Whether the \fI\%find_library()\fP command should automatically search
\fBlibx32\fP directories.
.sp
\fBFIND_LIBRARY_USE_LIBX32_PATHS\fP is a boolean specifying whether the
\fI\%find_library()\fP command should automatically search the \fBlibx32\fP
variant of directories called \fBlib\fP in the search path when building
x32\-abi binaries.
.sp
See also the \fI\%CMAKE_FIND_LIBRARY_CUSTOM_LIB_SUFFIX\fP variable.
.SS FIND_LIBRARY_USE_OPENBSD_VERSIONING
.sp
Whether \fI\%find_library()\fP should find OpenBSD\-style shared
libraries.
.sp
This property is a boolean specifying whether the
\fI\%find_library()\fP command should find shared libraries with
OpenBSD\-style versioned extension: \(dq.so.<major>.<minor>\(dq.  The
property is set to true on OpenBSD and false on other platforms.
.SS GENERATOR_IS_MULTI_CONFIG
.sp
Added in version 3.9.

.sp
Read\-only property that is true on multi\-configuration generators.
.sp
True when using a multi\-configuration generator such as:
.INDENT 0.0
.IP \(bu 2
\fI\%Ninja Multi\-Config\fP
.IP \(bu 2
\fI\%Visual Studio Generators\fP
.IP \(bu 2
\fI\%Xcode\fP
.UNINDENT
.sp
Multi\-config generators use \fI\%CMAKE_CONFIGURATION_TYPES\fP
as the set of configurations and ignore \fI\%CMAKE_BUILD_TYPE\fP\&.
.SS GLOBAL_DEPENDS_DEBUG_MODE
.sp
Enable global target dependency graph debug mode.
.sp
CMake automatically analyzes the global inter\-target dependency graph
at the beginning of native build system generation.  This property
causes it to display details of its analysis to stderr.
.SS GLOBAL_DEPENDS_NO_CYCLES
.sp
Disallow global target dependency graph cycles.
.sp
CMake automatically analyzes the global inter\-target dependency graph
at the beginning of native build system generation.  It reports an
error if the dependency graph contains a cycle that does not consist
of all STATIC library targets.  This property tells CMake to disallow
all cycles completely, even among static libraries.
.SS INSTALL_PARALLEL
.sp
Added in version 3.30.

.sp
Enables parallel installation option for a project. The install code for each
subdirectory added with \fBadd_subdirectory\fP can run independently.
.sp
When using the \fI\%Ninja Generators\fP, enabling this property causes
\fBinstall/local\fP targets have the console pool disabled, allowing them to run
concurrently.
.sp
This property also provides the target \fBinstall/parallel\fP, which has an
explicit dependency on the \fBinstall/local\fP target for each subdirectory.
.INDENT 0.0
.INDENT 3.5
Added in version 3.31.

.sp
When this property is enabled, \fBcmake \-\-install\fP can be given the \fB\-j <jobs>\fP
or \fB\-\-parallel <jobs>\fP option to specify a maximum number of jobs.
The \fI\%CMAKE_INSTALL_PARALLEL_LEVEL\fP environment variable specifies a
default parallel level if this option is not provided.
.UNINDENT
.UNINDENT
.sp
Calls to \fI\%install(CODE)\fP or \fI\%install(SCRIPT)\fP might depend
on actions performed by an earlier \fI\%install()\fP command in a different
directory such as files installed or variable settings. If the project has
such order\-dependent installation logic, parallel installation should be
not be enabled, in order to prevent possible race conditions.
.SS IN_TRY_COMPILE
.sp
Read\-only property that is true during a try\-compile configuration.
.sp
True when building a project inside a \fI\%try_compile()\fP or
\fI\%try_run()\fP command.
.SS JOB_POOLS
.sp
Ninja only: List of available pools.
.sp
A pool is a named integer property and defines the maximum number
of concurrent jobs which can be started by a rule assigned to the pool.
The \fBJOB_POOLS\fP property is a semicolon\-separated list of
pairs using the syntax \fBNAME=integer\fP (without a space after the equality sign).
.sp
For instance:
.INDENT 0.0
.INDENT 3.5
.sp
.EX
set_property(GLOBAL PROPERTY JOB_POOLS two_jobs=2 ten_jobs=10)
.EE
.UNINDENT
.UNINDENT
.sp
Defined pools could be used globally by setting
\fI\%CMAKE_JOB_POOL_COMPILE\fP and \fI\%CMAKE_JOB_POOL_LINK\fP
or per target by setting the target properties
\fI\%JOB_POOL_COMPILE\fP and \fI\%JOB_POOL_LINK\fP\&.
\fI\%Custom commands\fP and
\fI\%custom targets\fP can specify pools using the
option \fBJOB_POOL\fP\&.
Using a pool that is not defined by \fBJOB_POOLS\fP causes
an error by ninja at build time.
.sp
If not set, this property uses the value of the \fI\%CMAKE_JOB_POOLS\fP
variable.
.sp
Build targets provided by CMake that are meant for individual interactive
use, such as \fBinstall\fP, are placed in the \fBconsole\fP pool automatically.
.SS PACKAGES_FOUND
.sp
List of packages which were found during the CMake run.
.sp
List of packages which were found during the CMake run.  Whether a
package has been found is determined using the <NAME>_FOUND variables.
.SS PACKAGES_NOT_FOUND
.sp
List of packages which were not found during the CMake run.
.sp
List of packages which were not found during the CMake run.  Whether a
package has been found is determined using the <NAME>_FOUND variables.
.SS PREDEFINED_TARGETS_FOLDER
.sp
Name of FOLDER for targets that are added automatically by CMake.
.sp
If not set, CMake uses \(dqCMakePredefinedTargets\(dq as a default value for
this property.  Targets such as INSTALL, PACKAGE and RUN_TESTS will be
organized into this FOLDER.  See also the documentation for the
\fI\%FOLDER\fP target property.
.SS PROPAGATE_TOP_LEVEL_INCLUDES_TO_TRY_COMPILE
.sp
Added in version 3.30.

.sp
When this global property is set to true, the
\fI\%CMAKE_PROJECT_TOP_LEVEL_INCLUDES\fP variable is propagated into
\fI\%try_compile()\fP calls that use the
\fI\%whole\-project signature\fP\&.
Calls to the \fI\%source file signature\fP are not
affected by this property.
\fBPROPAGATE_TOP_LEVEL_INCLUDES_TO_TRY_COMPILE\fP is unset by default.
.sp
For \fI\%dependency providers\fP that want to
be enabled in whole\-project \fI\%try_compile()\fP calls, set this global
property to true just before or after registering the provider.
Note that all files listed in \fI\%CMAKE_PROJECT_TOP_LEVEL_INCLUDES\fP
will need to be able to handle being included in such \fI\%try_compile()\fP
calls, and it is the user\(aqs responsibility to ensure this.
.SS REPORT_UNDEFINED_PROPERTIES
.sp
If set, report any undefined properties to this file.
.sp
If this property is set to a filename then when CMake runs it will
report any properties or variables that were accessed but not defined
into the filename specified in this property.
.SS RULE_LAUNCH_COMPILE
.sp
Specify a launcher for compile rules.
.sp
\fBNOTE:\fP
.INDENT 0.0
.INDENT 3.5
This property is intended for internal use by \fI\%ctest(1)\fP\&.  Projects
and developers should use the \fI\%<LANG>_COMPILER_LAUNCHER\fP target
properties or the associated \fI\%CMAKE_<LANG>_COMPILER_LAUNCHER\fP
variables instead.
.UNINDENT
.UNINDENT
.sp
\fI\%Makefile Generators\fP and the \fI\%Ninja\fP generator prefix
compiler commands with the given launcher command line.
This is intended to allow launchers to intercept build problems
with high granularity.  Other generators ignore this property
because their underlying build systems provide no hook to wrap
individual commands with a launcher.
.SS RULE_LAUNCH_CUSTOM
.sp
Specify a launcher for custom rules.
.sp
\fI\%Makefile Generators\fP and the \fI\%Ninja\fP generator prefix
custom commands with the given launcher command line.
This is intended to allow launchers to intercept build problems
with high granularity.  Other generators ignore this property
because their underlying build systems provide no hook to wrap
individual commands with a launcher.
.SS RULE_LAUNCH_LINK
.sp
Specify a launcher for link rules.
.sp
\fBNOTE:\fP
.INDENT 0.0
.INDENT 3.5
This property is intended for internal use by \fI\%ctest(1)\fP\&.  Projects
and developers should use the \fI\%<LANG>_LINKER_LAUNCHER\fP target
properties or the associated \fI\%CMAKE_<LANG>_LINKER_LAUNCHER\fP
variables instead.
.UNINDENT
.UNINDENT
.sp
\fI\%Makefile Generators\fP and the \fI\%Ninja\fP generator prefix
link and archive commands with the given launcher command line.
This is intended to allow launchers to intercept build problems
with high granularity.  Other generators ignore this property
because their underlying build systems provide no hook to wrap
individual commands with a launcher.
.SS RULE_MESSAGES
.sp
Specify whether to report a message for each make rule.
.sp
This property specifies whether Makefile generators should add a
progress message describing what each build rule does.  If the
property is not set the default is ON.  Set the property to OFF to
disable granular messages and report only as each target completes.
This is intended to allow scripted builds to avoid the build time cost
of detailed reports.  If a \fI\%CMAKE_RULE_MESSAGES\fP cache entry exists
its value initializes the value of this property.  Non\-Makefile
generators currently ignore this property.
.SS TARGET_ARCHIVES_MAY_BE_SHARED_LIBS
.sp
Set if shared libraries may be named like archives.
.sp
On AIX shared libraries may be named \(dqlib<name>.a\(dq.  This property is
set to true on such platforms.
.SS TARGET_MESSAGES
.sp
Added in version 3.4.

.sp
Specify whether to report the completion of each target.
.sp
This property specifies whether \fI\%Makefile Generators\fP should
add a progress message describing that each target has been completed.
If the property is not set the default is \fBON\fP\&.  Set the property
to \fBOFF\fP to disable target completion messages.
.sp
This option is intended to reduce build output when little or no
work needs to be done to bring the build tree up to date.
.sp
If a \fBCMAKE_TARGET_MESSAGES\fP cache entry exists its value
initializes the value of this property.
.sp
Non\-Makefile generators currently ignore this property.
.sp
See the counterpart property \fI\%RULE_MESSAGES\fP to disable
everything except for target completion messages.
.SS TARGET_SUPPORTS_SHARED_LIBS
.sp
Does the target platform support shared libraries.
.sp
\fBTARGET_SUPPORTS_SHARED_LIBS\fP is a boolean specifying whether the target
platform supports shared libraries.  Basically all current general
purpose OS do so, the exceptions are usually embedded systems
with no or special OSs.
.SS USE_FOLDERS
.sp
Controls whether to use the \fI\%FOLDER\fP target property to organize
targets into folders.  The value of \fBUSE_FOLDERS\fP at the end of the top level
\fBCMakeLists.txt\fP file is what determines the behavior.
.sp
Changed in version 3.26: CMake treats this property as \fBON\fP by default.
See policy \fI\%CMP0143\fP\&.

.sp
Not all CMake generators support recording folder details for targets.
The \fI\%Xcode\fP and \fI\%Visual Studio\fP
generators are examples of generators that do.  Similarly, not all IDEs
support presenting targets using folder hierarchies, even if the CMake
generator used provides the necessary information.
.SS XCODE_EMIT_EFFECTIVE_PLATFORM_NAME
.sp
Added in version 3.8.

.sp
Control emission of \fBEFFECTIVE_PLATFORM_NAME\fP by the \fI\%Xcode\fP
generator.
.sp
It is required for building the same target with multiple SDKs. A
common use case is the parallel use of \fBiphoneos\fP and
\fBiphonesimulator\fP SDKs.
.sp
Three different states possible that control when the \fI\%Xcode\fP
generator emits the \fBEFFECTIVE_PLATFORM_NAME\fP variable:
.INDENT 0.0
.IP \(bu 2
If set to \fBON\fP it will always be emitted
.IP \(bu 2
If set to \fBOFF\fP it will never be emitted
.IP \(bu 2
If unset (the default) it will only be emitted when the project was
configured for an embedded Xcode SDK like iOS, tvOS, visionOS, watchOS
or any of the simulators.
.UNINDENT
.sp
\fBNOTE:\fP
.INDENT 0.0
.INDENT 3.5
When this behavior is enable for generated Xcode projects, the
\fBEFFECTIVE_PLATFORM_NAME\fP variable will leak into
\fI\%Generator expressions\fP
like \fBTARGET_FILE\fP and will render those mostly unusable.
.UNINDENT
.UNINDENT
.SH PROPERTIES ON DIRECTORIES
.SS ADDITIONAL_CLEAN_FILES
.sp
Added in version 3.15.

.sp
A \fI\%;\-list\fP of files or directories that will be
removed as a part of the global \fBclean\fP target.  It is useful for
specifying generated files or directories that are used by multiple targets
or by CMake itself, or that are generated in ways which cannot be captured as
outputs or byproducts of custom commands.
.sp
If an additional clean file is specific to a single target only, then the
\fI\%ADDITIONAL_CLEAN_FILES\fP target property would usually be a better
choice than this directory property.
.sp
Relative paths are allowed and are interpreted relative to the
current binary directory.
.sp
Contents of \fBADDITIONAL_CLEAN_FILES\fP may use
\fI\%generator expressions\fP\&.
.sp
This property only works for the \fI\%Ninja\fP and the Makefile
generators.  It is ignored by other generators.
.SS BINARY_DIR
.sp
Added in version 3.7.

.sp
This read\-only directory property reports absolute path to the binary
directory corresponding to the source on which it is read.
.SS BUILDSYSTEM_TARGETS
.sp
Added in version 3.7.

.sp
This read\-only directory property contains a
\fI\%semicolon\-separated list\fP of buildsystem targets added in the
directory by calls to the \fI\%add_library()\fP, \fI\%add_executable()\fP,
and \fI\%add_custom_target()\fP commands.  The list does not include any
\fI\%Imported Targets\fP or \fI\%Alias Targets\fP, but does include
\fI\%Interface Libraries\fP\&.  Each entry in the list is the logical name
of a target, suitable to pass to the \fI\%get_property()\fP command
\fBTARGET\fP option.
.sp
See also the \fI\%IMPORTED_TARGETS\fP directory property.
.SS CACHE_VARIABLES
.sp
List of cache variables available in the current directory.
.sp
This read\-only property specifies the list of CMake cache variables
currently defined.  It is intended for debugging purposes.
.SS CLEAN_NO_CUSTOM
.sp
Set to true to tell \fI\%Makefile Generators\fP not to remove the outputs of
custom commands for this directory during the \fBmake clean\fP operation.
This is ignored on other generators because it is not possible to implement.
.SS CMAKE_CONFIGURE_DEPENDS
.sp
Tell CMake about additional input files to the configuration process.
If any named file is modified the build system will re\-run CMake to
re\-configure the file and generate the build system again.
.sp
Specify files as a semicolon\-separated list of paths.  Relative paths
are interpreted as relative to the current source directory.
.SS COMPILE_DEFINITIONS
.sp
Preprocessor definitions for compiling a directory\(aqs sources.
.sp
This property specifies the list of options given so far to the
\fI\%add_compile_definitions()\fP (or \fI\%add_definitions()\fP) command.
.sp
The \fBCOMPILE_DEFINITIONS\fP property may be set to a semicolon\-separated
list of preprocessor definitions using the syntax \fBVAR\fP or \fBVAR=value\fP\&.
Function\-style definitions are not supported.  CMake will
automatically escape the value correctly for the native build system
(note that CMake language syntax may require escapes to specify some
values).
.sp
This property will be initialized in each directory by its value in the
directory\(aqs parent.
.sp
CMake will automatically drop some definitions that are not supported
by the native build tool.
.sp
Added in version 3.26: Any leading \fB\-D\fP on an item will be removed.

.sp
Disclaimer: Most native build tools have poor support for escaping
certain values.  CMake has work\-arounds for many cases but some values
may just not be possible to pass correctly.  If a value does not seem
to be escaped correctly, do not attempt to work\-around the problem by
adding escape sequences to the value.  Your work\-around may break in a
future version of CMake that has improved escape support.  Instead
consider defining the macro in a (configured) header file.  Then
report the limitation.  Known limitations include:
.INDENT 0.0
.INDENT 3.5
.TS
box center;
l|l.
T{
\fB#\fP
T}	T{
Broken almost everywhere.
T}
_
T{
\fB;\fP
T}	T{
Broken in VS IDE 7.0 and Borland Makefiles.
T}
_
T{
\fB,\fP
T}	T{
Broken in VS IDE.
T}
_
T{
\fB%\fP
T}	T{
Broken in some cases in NMake.
T}
_
T{
\fB& |\fP
T}	T{
Broken in some cases on MinGW.
T}
_
T{
\fB^ < > \e \(dq\fP
T}	T{
Broken in most Make tools on Windows.
T}
.TE
.UNINDENT
.UNINDENT
.sp
CMake does not reject these values outright because they do work in
some cases.  Use with caution.
.sp
Contents of \fBCOMPILE_DEFINITIONS\fP may use \(dqgenerator expressions\(dq with
the syntax \fB$<...>\fP\&.  See the \fI\%cmake\-generator\-expressions(7)\fP
manual for available expressions.  See the \fI\%cmake\-buildsystem(7)\fP
manual for more on defining buildsystem properties.
.sp
The corresponding \fI\%COMPILE_DEFINITIONS_<CONFIG>\fP property may
be set to specify per\-configuration definitions.  Generator expressions
should be preferred instead of setting the alternative property.
.SS COMPILE_OPTIONS
.sp
List of options to pass to the compiler.
.sp
This property holds a \fI\%semicolon\-separated list\fP of options
given so far to the \fI\%add_compile_options()\fP command.
.sp
This property is used to initialize the \fI\%COMPILE_OPTIONS\fP target
property when a target is created, which is used by the generators to set
the options for the compiler.
.sp
Contents of \fBCOMPILE_OPTIONS\fP may use \(dqgenerator expressions\(dq with the
syntax \fB$<...>\fP\&.  See the \fI\%cmake\-generator\-expressions(7)\fP manual
for available expressions.  See the \fI\%cmake\-buildsystem(7)\fP manual
for more on defining buildsystem properties.
.SS DEFINITIONS
.sp
For CMake 2.4 compatibility only.  Use \fI\%COMPILE_DEFINITIONS\fP
instead.
.sp
This read\-only property specifies the list of flags given so far to
the \fI\%add_definitions()\fP command.  It is intended for debugging
purposes.  Use the \fI\%COMPILE_DEFINITIONS\fP directory property
instead.
.sp
This built\-in read\-only property does not exist if policy
\fI\%CMP0059\fP is set to \fBNEW\fP\&.
.SS EXCLUDE_FROM_ALL
.sp
Set this directory property to a true value on a subdirectory to exclude
its targets from the \(dqall\(dq target of its ancestors.  If excluded, running
e.g. \fBmake\fP in the parent directory will not build targets in the
subdirectory by default.  This does not affect the \(dqall\(dq target of the
subdirectory itself.  Running e.g. \fBmake\fP inside the subdirectory will
still build its targets.
.sp
\fBEXCLUDE_FROM_ALL\fP is meant for when the subdirectory contains
a separate part of the project that is useful, but not necessary,
such as a set of examples, or e.g. an integrated 3rd party library.
Typically the subdirectory should contain its own \fI\%project()\fP
command invocation so that a full build system will be generated in the
subdirectory (such as a Visual Studio IDE solution file).  Note that
inter\-target dependencies supersede this exclusion.  If a target built by
the parent project depends on a target in the subdirectory, the dependee
target will be included in the parent project build system to satisfy
the dependency.
.sp
If the \fBEXCLUDE_FROM_ALL\fP argument is provided, it has the following effects:
.INDENT 0.0
.IP \(bu 2
Targets defined in the subdirectory or below will not be
included in the \fBALL\fP target of the parent directory.
Those targets must be built explicitly by the user,
or be a dependency of another target that will be built.
.IP \(bu 2
Targets defined in the subdirectory or below will be
excluded from IDE project files.
.IP \(bu 2
Any install rules defined in the subdirectory or below will
be ignored when installing the parent directory.
.UNINDENT
.sp
Note that these effects are not the same as those for the
\fI\%EXCLUDE_FROM_ALL\fP target property.
.SS IMPLICIT_DEPENDS_INCLUDE_TRANSFORM
.sp
Specify \fB#include\fP line transforms for dependencies in a directory.
.sp
This property specifies rules to transform macro\-like \fB#include\fP lines
during implicit dependency scanning of C and C++ source files.  The
list of rules must be semicolon\-separated with each entry of the form
\fBA_MACRO(%)=value\-with\-%\fP (the \fB%\fP must be literal).  During dependency
scanning occurrences of \fBA_MACRO(...)\fP on \fB#include\fP lines will be
replaced by the value given with the macro argument substituted for
\fB%\fP\&.  For example, the entry
.INDENT 0.0
.INDENT 3.5
.sp
.EX
MYDIR(%)=<mydir/%>
.EE
.UNINDENT
.UNINDENT
.sp
will convert lines of the form
.INDENT 0.0
.INDENT 3.5
.sp
.EX
#include MYDIR(myheader.h)
.EE
.UNINDENT
.UNINDENT
.sp
to
.INDENT 0.0
.INDENT 3.5
.sp
.EX
#include <mydir/myheader.h>
.EE
.UNINDENT
.UNINDENT
.sp
allowing the dependency to be followed.
.sp
This property applies to sources in all targets within a directory.
The property value is initialized in each directory by its value in
the directory\(aqs parent.
.SS IMPORTED_TARGETS
.sp
Added in version 3.21.

.sp
This read\-only directory property contains a
\fI\%semicolon\-separated list\fP of
\fI\%Imported Targets\fP added in the directory by calls to the
\fI\%add_library()\fP and \fI\%add_executable()\fP commands.
Each entry in the list is the logical name of a target, suitable
to pass to the \fI\%get_property()\fP command \fBTARGET\fP option
when called in the same directory.
.sp
See also the \fI\%BUILDSYSTEM_TARGETS\fP directory property.
.SS INCLUDE_DIRECTORIES
.sp
List of preprocessor include file search directories.
.sp
This property specifies the list of directories given so far to the
\fI\%include_directories()\fP command.
.sp
This property is used to populate the \fI\%INCLUDE_DIRECTORIES\fP
target property, which is used by the generators to set the include
directories for the compiler.
.sp
In addition to accepting values from that command, values may be set
directly on any directory using the \fI\%set_property()\fP command, and can be
set on the current directory using the \fI\%set_directory_properties()\fP
command.  A directory gets its initial value from its parent directory if it has
one.  The initial value of the \fI\%INCLUDE_DIRECTORIES\fP target property
comes from the value of this property.  Both directory and target property
values are adjusted by calls to the \fI\%include_directories()\fP command.
Calls to \fI\%set_property()\fP or \fI\%set_directory_properties()\fP,
however, will update the directory property value without updating target
property values.  Therefore direct property updates must be made before
calls to \fI\%add_executable()\fP or \fI\%add_library()\fP for targets
they are meant to affect.
.sp
The target property values are used by the generators to set the
include paths for the compiler.
.sp
Contents of \fBINCLUDE_DIRECTORIES\fP may use \(dqgenerator expressions\(dq with
the syntax \fB$<...>\fP\&.  See the \fI\%cmake\-generator\-expressions(7)\fP
manual for available expressions.  See the \fI\%cmake\-buildsystem(7)\fP
manual for more on defining buildsystem properties.
.SS INCLUDE_REGULAR_EXPRESSION
.sp
Include file scanning regular expression.
.sp
This property specifies the regular expression used during
dependency scanning to match include files that should be followed.
See the \fI\%include_regular_expression()\fP command for a high\-level
interface to set this property.
.SS LABELS
.sp
Added in version 3.10.

.sp
Specify a list of text labels associated with a directory and all of its
subdirectories. This is equivalent to setting the \fI\%LABELS\fP target
property and the \fI\%LABELS\fP test property on all targets and tests in
the current directory and subdirectories. Note: Launchers must enabled to
propagate labels to targets.
.sp
The \fI\%CMAKE_DIRECTORY_LABELS\fP variable can be used to initialize this
property.
.sp
The list is reported in dashboard submissions.
.SS LINK_DIRECTORIES
.sp
List of linker search directories.
.sp
This property holds a \fI\%semicolon\-separated list\fP of directories
and is typically populated using the \fI\%link_directories()\fP command.
It gets its initial value from its parent directory, if it has one.
.sp
The directory property is used to initialize the \fI\%LINK_DIRECTORIES\fP
target property when a target is created.  That target property is used
by the generators to set the library search directories for the linker.
.sp
Contents of \fBLINK_DIRECTORIES\fP may use \(dqgenerator expressions\(dq with
the syntax \fB$<...>\fP\&.  See the \fI\%cmake\-generator\-expressions(7)\fP
manual for available expressions.  See the \fI\%cmake\-buildsystem(7)\fP
manual for more on defining buildsystem properties.
.SS LINK_OPTIONS
.sp
Added in version 3.13.

.sp
List of options to use for the link step of shared library, module
and executable targets as well as the device link step.
.sp
This property holds a \fI\%semicolon\-separated list\fP of options
given so far to the \fI\%add_link_options()\fP command.
.sp
This property is used to initialize the \fI\%LINK_OPTIONS\fP target
property when a target is created, which is used by the generators to set
the options for the compiler.
.sp
Contents of \fBLINK_OPTIONS\fP may use \(dqgenerator expressions\(dq with the
syntax \fB$<...>\fP\&.  See the \fI\%cmake\-generator\-expressions(7)\fP manual
for available expressions.  See the \fI\%cmake\-buildsystem(7)\fP manual
for more on defining buildsystem properties.
.SS LISTFILE_STACK
.sp
The current stack of listfiles being processed.
.sp
This property is mainly useful when trying to debug errors in your
CMake scripts.  It returns a list of what list files are currently
being processed, in order.  So if one listfile does an
\fI\%include()\fP command then that is effectively pushing the
included listfile onto the stack.
.SS MACROS
.sp
List of macro commands available in the current directory.
.sp
This read\-only property specifies the list of CMake macros currently
defined.  It is intended for debugging purposes.  See the \fI\%macro()\fP
command.
.SS PARENT_DIRECTORY
.sp
Source directory that added current subdirectory.
.sp
This read\-only property specifies the source directory that added the
current source directory as a subdirectory of the build.  In the
top\-level directory the value is the empty\-string.
.SS RULE_LAUNCH_COMPILE
.sp
Specify a launcher for compile rules.
.sp
\fBNOTE:\fP
.INDENT 0.0
.INDENT 3.5
This property is intended for internal use by \fI\%ctest(1)\fP\&.  Projects
and developers should use the \fI\%<LANG>_COMPILER_LAUNCHER\fP target
properties or the associated \fI\%CMAKE_<LANG>_COMPILER_LAUNCHER\fP
variables instead.
.UNINDENT
.UNINDENT
.sp
See the \fI\%global property\fP of the same name
for details.  This overrides the global property for a directory.
.SS RULE_LAUNCH_CUSTOM
.sp
Specify a launcher for custom rules.
.sp
See the global property of the same name for details.  This overrides
the global property for a directory.
.SS RULE_LAUNCH_LINK
.sp
Specify a launcher for link rules.
.sp
\fBNOTE:\fP
.INDENT 0.0
.INDENT 3.5
This property is intended for internal use by \fI\%ctest(1)\fP\&.  Projects
and developers should use the \fI\%<LANG>_LINKER_LAUNCHER\fP target
properties or the associated \fI\%CMAKE_<LANG>_LINKER_LAUNCHER\fP
variables instead.
.UNINDENT
.UNINDENT
.sp
See the \fI\%global property\fP of the same name for
details.  This overrides the global property for a directory.
.SS SOURCE_DIR
.sp
Added in version 3.7.

.sp
This read\-only directory property reports absolute path to the source
directory on which it is read.
.SS SUBDIRECTORIES
.sp
Added in version 3.7.

.sp
This read\-only directory property contains a
\fI\%semicolon\-separated list\fP of subdirectories processed so far by
the \fI\%add_subdirectory()\fP or \fI\%subdirs()\fP commands.  Each entry is
the absolute path to the source directory (containing the \fBCMakeLists.txt\fP
file).  This is suitable to pass to the \fI\%get_property()\fP command
\fBDIRECTORY\fP option.
.sp
\fBNOTE:\fP
.INDENT 0.0
.INDENT 3.5
The \fI\%subdirs()\fP command does not process its arguments until
after the calling directory is fully processed.  Therefore looking
up this property in the current directory will not see them.
.UNINDENT
.UNINDENT
.SS SYSTEM
.sp
Added in version 3.25.

.sp
This directory property is used to initialize the \fI\%SYSTEM\fP
target property for non\-imported targets created in that directory.
It is set to true by \fI\%add_subdirectory()\fP and
\fI\%FetchContent_Declare()\fP when the \fBSYSTEM\fP option is given
as an argument to those commands.
.SS TESTS
.sp
Added in version 3.12.

.sp
List of tests.
.sp
This read\-only property holds a
\fI\%semicolon\-separated list\fP of tests
defined so far, in the current directory, by the \fI\%add_test()\fP command.
.SS TEST_INCLUDE_FILES
.sp
Added in version 3.10.

.sp
This directory property specifies a list of CMake scripts to be included and
processed when \fBctest\fP runs on the directory.  Use absolute paths, to avoid
ambiguity.  Script files are included in the specified order.
.sp
\fBTEST_INCLUDE_FILES\fP scripts are processed when running \fBctest\fP, not during
the \fBcmake\fP configuration phase.  These scripts should be written as if they
were CTest dashboard scripts.  It is common to generate such scripts dynamically
since many variables and commands available during configuration are not
accessible at test phase.
.SS Examples
.sp
Setting this directory property to append one or more CMake scripts:
.sp
CMakeLists.txt
.INDENT 0.0
.INDENT 3.5
.sp
.EX
configure_file(script.cmake.in script.cmake)

set_property(
  DIRECTORY
  APPEND
  PROPERTY TEST_INCLUDE_FILES
    ${CMAKE_CURRENT_BINARY_DIR}/script.cmake
    ${CMAKE_CURRENT_SOURCE_DIR}/foo.cmake
    ${dir}/bar.cmake
)
.EE
.UNINDENT
.UNINDENT
.sp
script.cmake.in
.INDENT 0.0
.INDENT 3.5
.sp
.EX
execute_process(
  COMMAND \(dq@CMAKE_COMMAND@\(dq \-E echo \(dqscript.cmake executed during CTest\(dq
)
.EE
.UNINDENT
.UNINDENT
.SS VARIABLES
.sp
List of variables defined in the current directory.
.sp
This read\-only property specifies the list of CMake variables
currently defined.  It is intended for debugging purposes.
.SS VS_GLOBAL_SECTION_POST_<section>
.sp
Specify a postSolution global section in Visual Studio.
.sp
Setting a property like this generates an entry of the following form
in the solution file:
.INDENT 0.0
.INDENT 3.5
.sp
.EX
GlobalSection(<section>) = postSolution
  <contents based on property value>
EndGlobalSection
.EE
.UNINDENT
.UNINDENT
.sp
The property must be set to a semicolon\-separated list of \fBkey=value\fP
pairs.  Each such pair will be transformed into an entry in the
solution global section.  Whitespace around key and value is ignored.
List elements which do not contain an equal sign are skipped.
.sp
This property only works for \fI\%Visual Studio Generators\fP; it is ignored
on other generators.  The property only applies when set on a
directory whose \fBCMakeLists.txt\fP contains a \fI\%project()\fP command.
.sp
Note that CMake generates postSolution sections \fBExtensibilityGlobals\fP
and \fBExtensibilityAddIns\fP by default.  If you set the corresponding
property, it will override the default section.  For example, setting
\fBVS_GLOBAL_SECTION_POST_ExtensibilityGlobals\fP will override the default
contents of the \fBExtensibilityGlobals\fP section, while keeping
ExtensibilityAddIns on its default.  However, CMake will always
add a \fBSolutionGuid\fP to the \fBExtensibilityGlobals\fP section
if it is not specified explicitly.
.SS VS_GLOBAL_SECTION_PRE_<section>
.sp
Specify a preSolution global section in Visual Studio.
.sp
Setting a property like this generates an entry of the following form
in the solution file:
.INDENT 0.0
.INDENT 3.5
.sp
.EX
GlobalSection(<section>) = preSolution
  <contents based on property value>
EndGlobalSection
.EE
.UNINDENT
.UNINDENT
.sp
The property must be set to a semicolon\-separated list of \fBkey=value\fP
pairs.  Each such pair will be transformed into an entry in the
solution global section.  Whitespace around key and value is ignored.
List elements which do not contain an equal sign are skipped.
.sp
This property only works for \fI\%Visual Studio Generators\fP; it is ignored
on other generators.  The property only applies when set on a
directory whose \fBCMakeLists.txt\fP contains a \fI\%project()\fP command.
.SS VS_SOLUTION_ITEMS
.sp
Added in version 4.0.

.sp
Specify solution level items included in the generated Visual Studio solution.
.sp
The \fI\%Visual Studio Generators\fP create a \fB\&.sln\fP file for each directory
whose \fBCMakeLists.txt\fP file calls the \fI\%project()\fP command. Append paths
to this property in the same directory as the top\-level \fI\%project()\fP
command call (e.g. in the top\-level \fBCMakeLists.txt\fP file) to specify files
included in the corresponding solution file.
.sp
If a file specified in \fBVS_SOLUTION_ITEMS\fP matches a \fI\%source_group()\fP
command call, the affected solution level items are placed in a hierarchy of
solution level folders according to the name specified in that command.
Otherwise the items are placed in a default solution level directory named
\fBSolution Items\fP\&. This name matches the default directory name used by Visual
Studio when attempting to add solution level items at the root of the solution.
.SS VS_STARTUP_PROJECT
.sp
Added in version 3.6.

.sp
Specify the default startup project in a Visual Studio solution.
.sp
The \fI\%Visual Studio Generators\fP create a \fB\&.sln\fP file for each directory
whose \fBCMakeLists.txt\fP file calls the \fI\%project()\fP command.  Set this
property in the same directory as a \fI\%project()\fP command call (e.g. in
the top\-level \fBCMakeLists.txt\fP file) to specify the default startup project
for the corresponding solution file.
.sp
The property must be set to the name of an existing target.  This
will cause that project to be listed first in the generated solution
file causing Visual Studio to make it the startup project if the
solution has never been opened before.
.sp
If this property is not specified, then the \fBALL_BUILD\fP project
will be the default.
.SH PROPERTIES ON TARGETS
.SS ADDITIONAL_CLEAN_FILES
.sp
Added in version 3.15.

.sp
A \fI\%;\-list\fP of files or directories that will be
removed as a part of the global \fBclean\fP target.  It can be used to specify
files and directories that are generated as part of building the target or
that are directly associated with the target in some way (e.g. created as a
result of running the target).
.sp
For custom targets, if such files can be captured as outputs or byproducts
instead, then that should be preferred over adding them to this property.
If an additional clean file is used by multiple targets or isn\(aqt
target\-specific, then the \fI\%ADDITIONAL_CLEAN_FILES\fP directory
property may be the more appropriate property to use.
.sp
Relative paths are allowed and are interpreted relative to the
current binary directory.
.sp
Contents of \fBADDITIONAL_CLEAN_FILES\fP may use
\fI\%generator expressions\fP\&.
.sp
This property only works for the \fI\%Ninja\fP and the Makefile
generators.  It is ignored by other generators.
.SS AIX_EXPORT_ALL_SYMBOLS
.sp
Added in version 3.17.

.sp
On AIX, CMake automatically exports all symbols from shared libraries, and
from executables with the \fI\%ENABLE_EXPORTS\fP target property set.
Explicitly disable this boolean property to suppress the behavior and
export no symbols by default.  In this case it is expected that the project
will use other means to export some symbols.
.sp
This property is initialized by the value of
the \fI\%CMAKE_AIX_EXPORT_ALL_SYMBOLS\fP variable if it is set
when a target is created.
.SS AIX_SHARED_LIBRARY_ARCHIVE
.sp
Added in version 3.31.

.sp
On AIX, enable or disable creation of a shared library archive
for a \fBSHARED\fP library target:
.INDENT 0.0
.IP \(bu 2
If enabled, the shared object \fB\&.so\fP file is placed inside
an archive \fB\&.a\fP file.  This is the preferred convention on AIX.
.sp
The shared object name in the archive encodes version information from
the \fI\%SOVERSION\fP target property, if set, and otherwise from
the \fI\%VERSION\fP target property, if set.
.IP \(bu 2
If disabled, a plain shared object \fB\&.so\fP file is produced.
This is consistent with other UNIX platforms.
.UNINDENT
.sp
This property defaults to \fI\%CMAKE_AIX_SHARED_LIBRARY_ARCHIVE\fP
if that variable is set when a non\-imported \fBSHARED\fP library target
is created by \fI\%add_library()\fP\&.  Imported targets must explicitly
enable \fBAIX_SHARED_LIBRARY_ARCHIVE\fP if they import an AIX
shared library archive.
.sp
Changed in version 4.0: For a non\-imported target, if this property is not set, the
default is \fIenabled\fP\&.  See policy \fI\%CMP0182\fP\&.
.sp
In CMake 3.31, policy \fI\%CMP0182\fP did not exist,
so the default was \fIdisabled\fP\&.
.sp
In CMake 3.30 and lower, \fBAIX_SHARED_LIBRARY_ARCHIVE\fP
did not exist, so the default was \fIdisabled\fP\&.

.SS ALIAS_GLOBAL
.sp
Added in version 3.18.

.sp
Read\-only property indicating of whether an \fI\%ALIAS target\fP
is globally visible.
.sp
The boolean value of this property is \fBTRUE\fP for aliases to
\fI\%IMPORTED targets\fP created
with the \fBGLOBAL\fP options to \fI\%add_executable()\fP or
\fI\%add_library()\fP, \fBFALSE\fP otherwise. It is undefined for
targets built within the project.
.sp
\fBNOTE:\fP
.INDENT 0.0
.INDENT 3.5
Promoting an \fI\%IMPORTED target\fP from \fBLOCAL\fP
to \fBGLOBAL\fP scope by changing the value or \fI\%IMPORTED_GLOBAL\fP
target property do not change the scope of local aliases.
.UNINDENT
.UNINDENT
.SS ALIASED_TARGET
.sp
Name of target aliased by this target.
.sp
If this is an \fI\%Alias Target\fP, this property contains
the name of the target aliased.
.SS ANDROID_ANT_ADDITIONAL_OPTIONS
.sp
Added in version 3.4.

.sp
Set the additional options for Android Ant build system. This is
a string value containing all command line options for the Ant build.
This property is initialized by the value of the
\fI\%CMAKE_ANDROID_ANT_ADDITIONAL_OPTIONS\fP variable if it is
set when a target is created.
.SS ANDROID_API
.sp
Added in version 3.1.

.sp
When \fI\%Cross Compiling for Android with NVIDIA Nsight Tegra Visual Studio Edition\fP, this property sets the Android target API version (e.g. \fB15\fP).
The version number must be a positive decimal integer.  This property is
initialized by the value of the \fI\%CMAKE_ANDROID_API\fP variable if
it is set when a target is created.
.SS ANDROID_API_MIN
.sp
Added in version 3.2.

.sp
Set the Android MIN API version (e.g. \fB9\fP).  The version number
must be a positive decimal integer.  This property is initialized by
the value of the \fI\%CMAKE_ANDROID_API_MIN\fP variable if it is set
when a target is created.  Native code builds using this API version.
.SS ANDROID_ARCH
.sp
Added in version 3.4.

.sp
When \fI\%Cross Compiling for Android with NVIDIA Nsight Tegra Visual Studio Edition\fP, this property sets the Android target architecture.
.sp
This is a string property that could be set to the one of
the following values:
.INDENT 0.0
.IP \(bu 2
\fBarmv7\-a\fP: \(dqARMv7\-A (armv7\-a)\(dq
.IP \(bu 2
\fBarmv7\-a\-hard\fP: \(dqARMv7\-A, hard\-float ABI (armv7\-a)\(dq
.IP \(bu 2
\fBarm64\-v8a\fP: \(dqARMv8\-A, 64bit (arm64\-v8a)\(dq
.IP \(bu 2
\fBx86\fP: \(dqx86 (x86)\(dq
.IP \(bu 2
\fBx86_64\fP: \(dqx86_64 (x86_64)\(dq
.UNINDENT
.sp
This property is initialized by the value of the
\fI\%CMAKE_ANDROID_ARCH\fP variable if it is set
when a target is created.
.SS ANDROID_ASSETS_DIRECTORIES
.sp
Added in version 3.4.

.sp
Set the Android assets directories to copy into the main assets
folder before build. This a string property that contains the
directory paths separated by semicolon.
This property is initialized by the value of the
\fI\%CMAKE_ANDROID_ASSETS_DIRECTORIES\fP variable if it is set when
a target is created.
.SS ANDROID_GUI
.sp
Added in version 3.1.

.sp
When \fI\%Cross Compiling for Android with NVIDIA Nsight Tegra Visual Studio Edition\fP, this property specifies whether to build an executable as an
application package on Android.
.sp
When this property is set to true the executable when built for Android
will be created as an application package.  This property is initialized
by the value of the \fI\%CMAKE_ANDROID_GUI\fP variable if it is set
when a target is created.
.sp
Add the \fBAndroidManifest.xml\fP source file explicitly to the
target \fI\%add_executable()\fP command invocation to specify the
root directory of the application package source.
.SS ANDROID_JAR_DEPENDENCIES
.sp
Added in version 3.4.

.sp
Set the Android property that specifies JAR dependencies.
This is a string value property. This property is initialized
by the value of the \fI\%CMAKE_ANDROID_JAR_DEPENDENCIES\fP
variable if it is set when a target is created.
.SS ANDROID_JAR_DIRECTORIES
.sp
Added in version 3.4.

.sp
Set the Android property that specifies directories to search for
the JAR libraries.
.sp
This a string property that contains the directory paths separated by
semicolons. This property is initialized by the value of the
\fI\%CMAKE_ANDROID_JAR_DIRECTORIES\fP variable if it is set when
a target is created.
.sp
Contents of \fBANDROID_JAR_DIRECTORIES\fP may use \(dqgenerator expressions\(dq
with the syntax \fB$<...>\fP\&.  See the \fI\%cmake\-generator\-expressions(7)\fP
manual for available expressions.
.SS ANDROID_JAVA_SOURCE_DIR
.sp
Added in version 3.4.

.sp
Set the Android property that defines the Java source code root directories.
This a string property that contains the directory paths separated by semicolon.
This property is initialized by the value of the
\fI\%CMAKE_ANDROID_JAVA_SOURCE_DIR\fP variable if it is set
when a target is created.
.SS ANDROID_NATIVE_LIB_DEPENDENCIES
.sp
Added in version 3.4.

.sp
Set the Android property that specifies the .so dependencies.
This is a string property.
.sp
This property is initialized by the value of the
\fI\%CMAKE_ANDROID_NATIVE_LIB_DEPENDENCIES\fP variable if it is set
when a target is created.
.sp
Contents of \fBANDROID_NATIVE_LIB_DEPENDENCIES\fP may use
\(dqgenerator expressions\(dq with the syntax \fB$<...>\fP\&. See the
\fI\%cmake\-generator\-expressions(7)\fP manual for
available expressions.
.SS ANDROID_NATIVE_LIB_DIRECTORIES
.sp
Added in version 3.4.

.sp
Set the Android property that specifies directories to search for the \fB\&.so\fP
libraries.
.sp
This a string property that contains the directory paths separated
by semicolons.
.sp
This property is initialized by the value of the
\fI\%CMAKE_ANDROID_NATIVE_LIB_DIRECTORIES\fP variable if it is set when a
target is created.
.sp
Contents of \fBANDROID_NATIVE_LIB_DIRECTORIES\fP may use \(dqgenerator expressions\(dq
with the syntax \fB$<...>\fP\&.  See the \fI\%cmake\-generator\-expressions(7)\fP
manual for available expressions.
.SS ANDROID_PROCESS_MAX
.sp
Added in version 3.4.

.sp
Set the Android property that defines the maximum number of a
parallel Android NDK compiler processes (e.g. \fB4\fP).
This property is initialized by the value of the
\fI\%CMAKE_ANDROID_PROCESS_MAX\fP variable if it is set
when a target is created.
.SS ANDROID_PROGUARD
.sp
Added in version 3.4.

.sp
When this property is set to true that enables the ProGuard tool to shrink,
optimize, and obfuscate the code by removing unused code and renaming
classes, fields, and methods with semantically obscure names.
This property is initialized by the value of the
\fI\%CMAKE_ANDROID_PROGUARD\fP variable if it is set
when a target is created.
.SS ANDROID_PROGUARD_CONFIG_PATH
.sp
Added in version 3.4.

.sp
Set the Android property that specifies the location of the ProGuard
config file. Leave empty to use the default one.
This a string property that contains the path to ProGuard config file.
This property is initialized by the value of the
\fI\%CMAKE_ANDROID_PROGUARD_CONFIG_PATH\fP variable if it is set
when a target is created.
.SS ANDROID_SECURE_PROPS_PATH
.sp
Added in version 3.4.

.sp
Set the Android property that states the location of the secure properties file.
This is a string property that contains the file path.
This property is initialized by the value of the
\fI\%CMAKE_ANDROID_SECURE_PROPS_PATH\fP variable
if it is set when a target is created.
.SS ANDROID_SKIP_ANT_STEP
.sp
Added in version 3.4.

.sp
Set the Android property that defines whether or not to skip the Ant build step.
This is a boolean property initialized by the value of the
\fI\%CMAKE_ANDROID_SKIP_ANT_STEP\fP variable if it is set when a target is created.
.SS ANDROID_STL_TYPE
.sp
Added in version 3.4.

.sp
When \fI\%Cross Compiling for Android with NVIDIA Nsight Tegra Visual Studio Edition\fP, this property specifies the type of STL support for the project.
This is a string property that could set to the one of the following values:
.INDENT 0.0
.TP
.B \fBnone\fP
No C++ Support
.TP
.B \fBsystem\fP
Minimal C++ without STL
.TP
.B \fBgabi++_static\fP
GAbi++ Static
.TP
.B \fBgabi++_shared\fP
GAbi++ Shared
.TP
.B \fBgnustl_static\fP
GNU libstdc++ Static
.TP
.B \fBgnustl_shared\fP
GNU libstdc++ Shared
.TP
.B \fBstlport_static\fP
STLport Static
.TP
.B \fBstlport_shared\fP
STLport Shared
.UNINDENT
.sp
This property is initialized by the value of the
\fI\%CMAKE_ANDROID_STL_TYPE\fP variable if it is set when a target is
created.
.SS ARCHIVE_OUTPUT_DIRECTORY
.sp
Output directory in which to build \fI\%ARCHIVE\fP target files.
.sp
This property specifies the directory into which archive target files
should be built.  The property value may use
\fI\%generator expressions\fP\&.
Multi\-configuration generators (\fI\%Visual Studio\fP,
\fI\%Xcode\fP, \fI\%Ninja Multi\-Config\fP) append a
per\-configuration subdirectory to the specified directory unless a generator
expression is used.
.sp
This property is initialized by the value of the
\fI\%CMAKE_ARCHIVE_OUTPUT_DIRECTORY\fP variable if it is set when a target is created.
.sp
\fBNOTE:\fP
.INDENT 0.0
.INDENT 3.5
On macOS, this property will be ignored for the linker import files (e.g.
\fB\&.tbd\fP files, see \fI\%ENABLE_EXPORTS\fP property for details) when:
.INDENT 0.0
.IP \(bu 2
The \fI\%FRAMEWORK\fP is set, because the framework layout cannot be
changed.
.IP \(bu 2
The \fI\%Xcode\fP generator is used, due to the limitations and
constraints of the \fBXcode\fP tool.
.UNINDENT
.sp
In both cases, the linker import files will be generated in the same directory as the shared
library.
.UNINDENT
.UNINDENT
.sp
See also the \fI\%ARCHIVE_OUTPUT_DIRECTORY_<CONFIG>\fP target property.
.SS ARCHIVE_OUTPUT_DIRECTORY_<CONFIG>
.sp
Per\-configuration output directory for
\fI\%ARCHIVE\fP target files.
.sp
This is a per\-configuration version of the
\fI\%ARCHIVE_OUTPUT_DIRECTORY\fP target property, but
multi\-configuration generators (\fI\%Visual Studio\fP, \fI\%Xcode\fP, \fI\%Ninja Multi\-Config\fP) do NOT
append a per\-configuration subdirectory to the specified directory.  This
property is initialized by the value of the
\fI\%CMAKE_ARCHIVE_OUTPUT_DIRECTORY_<CONFIG>\fP variable if
it is set when a target is created.
.sp
Contents of \fBARCHIVE_OUTPUT_DIRECTORY_<CONFIG>\fP may use
\fI\%generator expressions\fP\&.
.SS ARCHIVE_OUTPUT_NAME
.sp
Output name for \fI\%ARCHIVE\fP target files.
.sp
This property specifies the base name for archive target files.  It
overrides \fI\%OUTPUT_NAME\fP and \fI\%OUTPUT_NAME_<CONFIG>\fP
properties.
.sp
\fBNOTE:\fP
.INDENT 0.0
.INDENT 3.5
On macOS, this property will be ignored for the linker import files (e.g.
\fB\&.tbd\fP files, see \fI\%ENABLE_EXPORTS\fP property for details) when:
.INDENT 0.0
.IP \(bu 2
The \fI\%FRAMEWORK\fP is set, because the framework layout cannot be
changed.
.IP \(bu 2
The \fI\%Xcode\fP generator is used, due to the limitations and
constraints of the \fBXcode\fP tool.
.UNINDENT
.sp
In both cases, the linker import files will be generated with the same name as the shared
library.
.UNINDENT
.UNINDENT
.sp
See also the \fI\%ARCHIVE_OUTPUT_NAME_<CONFIG>\fP target property.
.SS ARCHIVE_OUTPUT_NAME_<CONFIG>
.sp
Per\-configuration output name for
\fI\%ARCHIVE\fP target files.
.sp
This is the configuration\-specific version of the
\fI\%ARCHIVE_OUTPUT_NAME\fP target property.
.SS AUTOGEN_BETTER_GRAPH_MULTI_CONFIG
.sp
Added in version 3.29.

.sp
\fBAUTOGEN_BETTER_GRAPH_MULTI_CONFIG\fP is a boolean property that can be set
on a target to have better dependency graph for multi\-configuration generators.
When this property is enabled, \fBCMake\fP will generate more per\-config targets.
Thus, the dependency graph will be more accurate for multi\-configuration
generators and some recompilations will be avoided.
.sp
If the Qt version is 6.8 or newer, this property is enabled by default.
If the Qt version is older than 6.8, this property is disabled by default.
Consult the Qt documentation to check if the property can be enabled for older
Qt versions.
.sp
See the \fI\%cmake\-qt(7)\fP manual for more information on using CMake
with Qt.
.sp
This property is initialized by the
\fI\%CMAKE_AUTOGEN_BETTER_GRAPH_MULTI_CONFIG\fP variable if it is set when
a target is created.
.SS AUTOGEN_BUILD_DIR
.sp
Added in version 3.9.

.sp
Directory where \fI\%AUTOMOC\fP, \fI\%AUTOUIC\fP and \fI\%AUTORCC\fP
generate files for the target.
.sp
The directory is created on demand and automatically added to the
\fI\%ADDITIONAL_CLEAN_FILES\fP target property.
.sp
When unset or empty the directory \fB<dir>/<target\-name>_autogen\fP is used where
\fB<dir>\fP is \fI\%CMAKE_CURRENT_BINARY_DIR\fP and \fB<target\-name>\fP
is \fI\%NAME\fP\&.
.sp
By default \fBAUTOGEN_BUILD_DIR\fP is unset.
.sp
See the \fI\%cmake\-qt(7)\fP manual for more information on using CMake
with Qt.
.SS AUTOGEN_COMMAND_LINE_LENGTH_MAX
.sp
Added in version 3.29.

.sp
Command line length limit for autogen targets, i.e. \fBmoc\fP or \fBuic\fP,
that triggers the use of response files on Windows instead of passing all
arguments to the command line.
.INDENT 0.0
.IP \(bu 2
An empty (or unset) value sets the limit to 32000
.IP \(bu 2
A positive non zero integer value sets the exact command line length
limit.
.UNINDENT
.sp
By default \fBAUTOGEN_COMMAND_LINE_LENGTH_MAX\fP is initialized from
\fI\%CMAKE_AUTOGEN_COMMAND_LINE_LENGTH_MAX\fP\&.
.sp
See the \fI\%cmake\-qt(7)\fP manual for more information on using CMake
with Qt.
.SS AUTOGEN_ORIGIN_DEPENDS
.sp
Added in version 3.14.

.sp
Switch for forwarding origin target dependencies to the corresponding
\fI\%The <ORIGIN>_autogen target\fP target.
.INDENT 0.0
.INDENT 3.5
.sp
\fBNOTE:\fP
.INDENT 0.0
.INDENT 3.5
If Qt 5.15 or later is used and the generator is either \fI\%Ninja\fP
or \fI\%Makefile Generators\fP, origin target dependencies are forwarded to
the \fI\%The <ORIGIN>_autogen_timestamp_deps target\fP target instead of
\fI\%The <ORIGIN>_autogen target\fP
.UNINDENT
.UNINDENT
.UNINDENT
.UNINDENT
.sp
Targets which have their \fI\%AUTOMOC\fP or \fI\%AUTOUIC\fP property
\fBON\fP have a corresponding \fI\%The <ORIGIN>_autogen target\fP target which generates
\fBmoc\fP and \fBuic\fP files.  As this \fI\%The <ORIGIN>_autogen target\fP target is created at
generate\-time, it is not possible to define dependencies of it using
e.g.  \fI\%add_dependencies()\fP\&.  Instead the \fBAUTOGEN_ORIGIN_DEPENDS\fP
target property decides whether the origin target dependencies should be
forwarded to the \fI\%The <ORIGIN>_autogen target\fP target or not.
.sp
By default \fBAUTOGEN_ORIGIN_DEPENDS\fP is initialized from
\fI\%CMAKE_AUTOGEN_ORIGIN_DEPENDS\fP which is \fBON\fP by default.
.sp
In total the dependencies of the \fI\%The <ORIGIN>_autogen target\fP target are composed
from
.INDENT 0.0
.IP \(bu 2
forwarded origin target dependencies
(enabled by default via \fBAUTOGEN_ORIGIN_DEPENDS\fP)
.IP \(bu 2
additional user defined dependencies from \fI\%AUTOGEN_TARGET_DEPENDS\fP
.UNINDENT
.sp
See the \fI\%cmake\-qt(7)\fP manual for more information on using CMake
with Qt.
.sp
\fBNOTE:\fP
.INDENT 0.0
.INDENT 3.5
Disabling \fBAUTOGEN_ORIGIN_DEPENDS\fP is useful to avoid building of
origin target dependencies when building the \fI\%The <ORIGIN>_autogen target\fP target
only. This is especially interesting when a
\fI\%global autogen target\fP is enabled.
.sp
When the \fI\%The <ORIGIN>_autogen target\fP target doesn\(aqt require all the origin target\(aqs
dependencies, and \fBAUTOGEN_ORIGIN_DEPENDS\fP is disabled, it might be
necessary to extend \fI\%AUTOGEN_TARGET_DEPENDS\fP to add missing
dependencies.
.UNINDENT
.UNINDENT
.SS AUTOGEN_PARALLEL
.sp
Added in version 3.11.

.sp
Number of parallel \fBmoc\fP or \fBuic\fP processes to start when using
\fI\%AUTOMOC\fP and \fI\%AUTOUIC\fP\&.
.sp
The custom \fI\%The <ORIGIN>_autogen target\fP target starts a number of threads of which
each one parses a source file and on demand starts a \fBmoc\fP or \fBuic\fP
process. \fBAUTOGEN_PARALLEL\fP controls how many parallel threads
(and therefore \fBmoc\fP or \fBuic\fP processes) are started.
.INDENT 0.0
.IP \(bu 2
An empty (or unset) value or the string \fBAUTO\fP sets the number of
threads/processes to the number of physical CPUs on the host system.
.IP \(bu 2
A positive non zero integer value sets the exact thread/process count.
.IP \(bu 2
Otherwise a single thread/process is started.
.UNINDENT
.sp
By default \fBAUTOGEN_PARALLEL\fP is initialized from
\fI\%CMAKE_AUTOGEN_PARALLEL\fP\&.
.sp
See the \fI\%cmake\-qt(7)\fP manual for more information on using CMake
with Qt.
.SS AUTOGEN_TARGET_DEPENDS
.sp
Additional target dependencies of the corresponding \fI\%The <ORIGIN>_autogen target\fP
target.
.INDENT 0.0
.INDENT 3.5
.sp
\fBNOTE:\fP
.INDENT 0.0
.INDENT 3.5
If Qt 5.15 or later is used and the generator is either \fI\%Ninja\fP
or \fI\%Makefile Generators\fP, additional target dependencies are added to
the \fI\%The <ORIGIN>_autogen_timestamp_deps target\fP target instead of the
\fI\%The <ORIGIN>_autogen target\fP target.
.UNINDENT
.UNINDENT
.UNINDENT
.UNINDENT
.sp
Targets which have their \fI\%AUTOMOC\fP or \fI\%AUTOUIC\fP property
\fBON\fP have a corresponding \fI\%The <ORIGIN>_autogen target\fP  target which generates
\fBmoc\fP and \fBuic\fP files.  As this \fI\%The <ORIGIN>_autogen target\fP  target is created
at generate\-time, it is not possible to define dependencies of it using e.g.
\fI\%add_dependencies()\fP\&.  Instead the \fBAUTOGEN_TARGET_DEPENDS\fP target
property can be set to a \fI\%;\-list\fP of additional
dependencies for the \fI\%The <ORIGIN>_autogen target\fP  target. Dependencies can be target
names or file names.
.sp
In total the dependencies of the \fI\%The <ORIGIN>_autogen target\fP  target are composed
from
.INDENT 0.0
.IP \(bu 2
forwarded origin target dependencies
(enabled by default via \fI\%AUTOGEN_ORIGIN_DEPENDS\fP)
.IP \(bu 2
additional user defined dependencies from \fBAUTOGEN_TARGET_DEPENDS\fP
.UNINDENT
.sp
See the \fI\%cmake\-qt(7)\fP manual for more information on using CMake
with Qt.
.SS Use cases
.sp
If \fI\%AUTOMOC\fP or \fI\%AUTOUIC\fP depends on a file that is either
.INDENT 0.0
.IP \(bu 2
a \fI\%GENERATED\fP non C++ file (e.g. a \fI\%GENERATED\fP \fB\&.json\fP
or \fB\&.ui\fP file) or
.IP \(bu 2
a \fI\%GENERATED\fP C++ file that isn\(aqt recognized by \fI\%AUTOMOC\fP
and \fI\%AUTOUIC\fP because it\(aqs skipped by \fI\%SKIP_AUTOMOC\fP,
\fI\%SKIP_AUTOUIC\fP, \fI\%SKIP_AUTOGEN\fP or \fI\%CMP0071\fP or
.IP \(bu 2
a file that isn\(aqt in the origin target\(aqs sources
.UNINDENT
.sp
it must be added to \fBAUTOGEN_TARGET_DEPENDS\fP\&.
.SS AUTOGEN_USE_SYSTEM_INCLUDE
.sp
Added in version 3.27.

.sp
\fBAUTOGEN_USE_SYSTEM_INCLUDE\fP is a boolean property that can be set
on a target to indicate that the autogen target include directory should
be added as a system include directory or normal include directory to the
target.
.sp
If this property is not set, the autogen target include directory is added
as a system include directory by default.  See policy \fI\%CMP0151\fP\&.
.sp
See the \fI\%cmake\-qt(7)\fP manual for more information on using CMake
with Qt.
.sp
This property is initialized by the
\fI\%CMAKE_AUTOGEN_USE_SYSTEM_INCLUDE\fP variable if it is set when
a target is created.
.SS AUTOMOC
.sp
Should the target be processed with auto\-moc (for Qt projects).
.sp
\fBAUTOMOC\fP is a boolean specifying whether CMake will handle the Qt \fBmoc\fP
preprocessor automatically, i.e.  without having to use commands like
\fI\%qt4_wrap_cpp()\fP, \X'tty: link https://doc.qt.io/archives/qt-5.15/qtcore-cmake-qt5-wrap-cpp.html'\fI\%qt5_wrap_cpp()\fP\X'tty: link', etc.
Currently, Qt versions 4 to 6 are supported.
.sp
This property is initialized by the value of the \fI\%CMAKE_AUTOMOC\fP
variable if it is set when a target is created.
.sp
When this property is set \fBON\fP, CMake will scan the header and
source files at build time and invoke \fBmoc\fP accordingly.
.SS Header file processing
.sp
At configuration time, a list of header files that should be scanned by
\fBAUTOMOC\fP is computed from the target\(aqs sources.
.INDENT 0.0
.IP \(bu 2
All header files in the target\(aqs sources are added to the scan list.
.IP \(bu 2
For all C++ source files \fB<source_base>.<source_extension>\fP in the
target\(aqs sources, CMake searches for
.INDENT 2.0
.IP \(bu 2
a regular header with the same base name
(\fB<source_base>.<header_extension>\fP) and
.IP \(bu 2
a private header with the same base name and a \fB_p\fP suffix
(\fB<source_base>_p.<header_extension>\fP)
.UNINDENT
.sp
and adds these to the scan list.
.IP \(bu 2
The \fI\%AUTOMOC_INCLUDE_DIRECTORIES\fP target property may be set
to explicitly tell \fBmoc\fP what include directories to search.  If not
set, the default is to use the include directories from the target and
its transitive closure of dependencies.
.UNINDENT
.sp
At build time, CMake scans each unknown or modified header file from the
list and searches for
.INDENT 0.0
.IP \(bu 2
a Qt macro from \fI\%AUTOMOC_MACRO_NAMES\fP,
.IP \(bu 2
additional file dependencies from the \fBFILE\fP argument of a
\fBQ_PLUGIN_METADATA\fP macro and
.IP \(bu 2
additional file dependencies detected by filters defined in
\fI\%AUTOMOC_DEPEND_FILTERS\fP\&.
.UNINDENT
.sp
If a Qt macro is found, then the header will be compiled by the \fBmoc\fP to the
output file \fBmoc_<base_name>.cpp\fP\&.  The complete output file path is
described in the section \fI\%Output file location\fP\&.
.sp
The header will be \fBmoc\fP compiled again if a file from the additional file
dependencies changes.
.sp
Header \fBmoc\fP output files \fBmoc_<base_name>.cpp\fP can be included in source
files.  In the section \fI\%Including header moc files in sources\fP there is more
information on that topic.
.SS Source file processing
.sp
At build time, CMake scans each unknown or modified C++ source file from the
target\(aqs sources for
.INDENT 0.0
.IP \(bu 2
a Qt macro from \fI\%AUTOMOC_MACRO_NAMES\fP,
.IP \(bu 2
includes of header \fBmoc\fP files
(see \fI\%Including header moc files in sources\fP),
.IP \(bu 2
additional file dependencies from the \fBFILE\fP argument of a
\fBQ_PLUGIN_METADATA\fP macro and
.IP \(bu 2
additional file dependencies detected by filters defined in
\fI\%AUTOMOC_DEPEND_FILTERS\fP\&.
.UNINDENT
.sp
If a Qt macro is found, then the C++ source file
\fB<base>.<source_extension>\fP is expected to as well contain an include
statement
.INDENT 0.0
.INDENT 3.5
.sp
.EX
#include <<base>.moc> // or
#include \(dq<base>.moc\(dq
.EE
.UNINDENT
.UNINDENT
.sp
The source file then will be compiled by the \fBmoc\fP to the output file
\fB<base>.moc\fP\&.  A description of the complete output file path is in section
\fI\%Output file location\fP\&.
.sp
The source will be \fBmoc\fP compiled again if a file from the additional file
dependencies changes.
.SS Including header moc files in sources
.sp
A source file can include the \fBmoc\fP output file of a header
\fB<header_base>.<header_extension>\fP by using an include statement of
the form
.INDENT 0.0
.INDENT 3.5
.sp
.EX
#include <moc_<header_base>.cpp> // or
#include \(dqmoc_<header_base>.cpp\(dq
.EE
.UNINDENT
.UNINDENT
.sp
If the \fBmoc\fP output file of a header is included by a source, it will
be generated in a different location than if it was not included.  This is
described in the section \fI\%Output file location\fP\&.
.SS Output file location
.SS Included moc output files
.sp
\fBmoc\fP output files that are included by a source file will be generated in
.INDENT 0.0
.IP \(bu 2
\fB<AUTOGEN_BUILD_DIR>/include\fP
for single configuration generators or in
.IP \(bu 2
\fB<AUTOGEN_BUILD_DIR>/include_<CONFIG>\fP
for \fI\%multi configuration\fP generators.
.UNINDENT
.sp
Where \fB<AUTOGEN_BUILD_DIR>\fP is the value of the target property
\fI\%AUTOGEN_BUILD_DIR\fP\&.
.sp
The include directory is automatically added to the target\(aqs
\fI\%INCLUDE_DIRECTORIES\fP\&.
.SS Not included moc output files
.sp
\fBmoc\fP output files that are not included in a source file will be generated
in
.INDENT 0.0
.IP \(bu 2
\fB<AUTOGEN_BUILD_DIR>/<SOURCE_DIR_CHECKSUM>\fP
for single configuration generators or in,
.IP \(bu 2
\fB<AUTOGEN_BUILD_DIR>/include_<CONFIG>/<SOURCE_DIR_CHECKSUM>\fP
for \fI\%multi configuration\fP generators.
.UNINDENT
.sp
Where \fB<SOURCE_DIR_CHECKSUM>\fP is a checksum computed from the relative
parent directory path of the \fBmoc\fP input file.  This scheme allows to have
\fBmoc\fP input files with the same name in different directories.
.sp
All not included \fBmoc\fP output files will be included automatically by the
CMake generated file
.INDENT 0.0
.IP \(bu 2
\fB<AUTOGEN_BUILD_DIR>/mocs_compilation.cpp\fP, or
.IP \(bu 2
\fB<AUTOGEN_BUILD_DIR>/mocs_compilation_$<CONFIG>.cpp\fP,
.UNINDENT
.sp
which is added to the target\(aqs sources.
.SS Qt version detection
.sp
\fBAUTOMOC\fP enabled targets need to know the Qt major and minor
version they\(aqre working with.  The major version usually is provided by the
\fBINTERFACE_QT_MAJOR_VERSION\fP property of the \fBQt[456]Core\fP library,
that the target links to.  To find the minor version, CMake builds a list of
available Qt versions from
.INDENT 0.0
.IP \(bu 2
\fBQt6Core_VERSION_MAJOR\fP and \fBQt6Core_VERSION_MINOR\fP variables
(usually set by \fBfind_package(Qt6...)\fP)
.IP \(bu 2
\fBQt6Core_VERSION_MAJOR\fP and \fBQt6Core_VERSION_MINOR\fP directory properties
.IP \(bu 2
\fBQt5Core_VERSION_MAJOR\fP and \fBQt5Core_VERSION_MINOR\fP variables
(usually set by \fBfind_package(Qt5...)\fP)
.IP \(bu 2
\fBQt5Core_VERSION_MAJOR\fP and \fBQt5Core_VERSION_MINOR\fP directory properties
.IP \(bu 2
\fBQT_VERSION_MAJOR\fP and \fBQT_VERSION_MINOR\fP  variables
(usually set by \fBfind_package(Qt4...)\fP)
.IP \(bu 2
\fBQT_VERSION_MAJOR\fP and \fBQT_VERSION_MINOR\fP  directory properties
.UNINDENT
.sp
in the context of the \fI\%add_executable()\fP or \fI\%add_library()\fP call.
.sp
Assumed  \fBINTERFACE_QT_MAJOR_VERSION\fP is a valid number, the first
entry in the list with a matching major version is taken.  If no matching major
version was found, an error is generated.
If  \fBINTERFACE_QT_MAJOR_VERSION\fP is not a valid number, the first
entry in the list is taken.
.sp
A \fBfind_package(Qt[456]...)\fP call sets the \fBQT/Qt[56]Core_VERSION_MAJOR/MINOR\fP
variables.  If the call is in a different context than the
\fI\%add_executable()\fP or \fI\%add_library()\fP call, e.g. in a function,
then the version variables might not be available to the \fBAUTOMOC\fP
enabled target.
In that case the version variables can be forwarded from the
\fBfind_package(Qt[456]...)\fP calling context to the \fI\%add_executable()\fP
or \fI\%add_library()\fP calling context as directory properties.
The following Qt5 example demonstrates the procedure.
.INDENT 0.0
.INDENT 3.5
.sp
.EX
function (add_qt5_client)
  find_package(Qt5 REQUIRED QUIET COMPONENTS Core Widgets)
  ...
  set_property(DIRECTORY \(dq${CMAKE_CURRENT_SOURCE_DIR}\(dq
    PROPERTY Qt5Core_VERSION_MAJOR \(dq${Qt5Core_VERSION_MAJOR}\(dq)
  set_property(DIRECTORY \(dq${CMAKE_CURRENT_SOURCE_DIR}\(dq
    PROPERTY Qt5Core_VERSION_MINOR \(dq${Qt5Core_VERSION_MAJOR}\(dq)
  ...
endfunction ()
\&...
add_qt5_client()
add_executable(myTarget main.cpp)
target_link_libraries(myTarget Qt5::QtWidgets)
set_property(TARGET myTarget PROPERTY AUTOMOC ON)
.EE
.UNINDENT
.UNINDENT
.SS Modifiers
.sp
\fI\%AUTOMOC_EXECUTABLE\fP:
The \fBmoc\fP executable will be detected automatically, but can be forced to
a certain binary using this target property.
.sp
\fI\%AUTOMOC_MOC_OPTIONS\fP:
Additional command line options for \fBmoc\fP can be set in this target property.
.sp
\fI\%AUTOMOC_MACRO_NAMES\fP:
This list of Qt macro names can be extended to search for additional macros in
headers and sources.
.sp
\fI\%AUTOMOC_DEPEND_FILTERS\fP:
\fBmoc\fP dependency file names can be extracted from headers or sources by
defining file name filters in this target property.
.sp
\fI\%AUTOMOC_COMPILER_PREDEFINES\fP:
Compiler pre definitions for \fBmoc\fP are written to the \fBmoc_predefs.h\fP file.
The generation of this file can be enabled or disabled in this target property.
.sp
\fI\%AUTOMOC_INCLUDE_DIRECTORIES\fP:
Specifies one or more include directories for \fBAUTOMOC\fP to pass explicitly to \fBmoc\fP
instead of automatically discovering a target’s include directories.
.sp
\fI\%SKIP_AUTOMOC\fP:
Sources and headers can be excluded from \fBAUTOMOC\fP processing by
setting this source file property.
.sp
\fI\%SKIP_AUTOGEN\fP:
Source files can be excluded from \fBAUTOMOC\fP,
\fI\%AUTOUIC\fP and \fI\%AUTORCC\fP processing by
setting this source file property.
.sp
\fI\%AUTOGEN_SOURCE_GROUP\fP:
This global property can be used to group files generated by
\fBAUTOMOC\fP or \fI\%AUTORCC\fP together in an IDE, e.g.  in MSVS.
.sp
\fI\%AUTOGEN_TARGETS_FOLDER\fP:
This global property can be used to group \fBAUTOMOC\fP,
\fI\%AUTOUIC\fP and \fI\%AUTORCC\fP targets together in an IDE,
e.g.  in MSVS.
.sp
\fI\%CMAKE_GLOBAL_AUTOGEN_TARGET\fP:
A global \fBautogen\fP target, that depends on all \fBAUTOMOC\fP or
\fI\%AUTOUIC\fP generated \fI\%The <ORIGIN>_autogen target\fP targets in the project,
will be generated when this variable is \fBON\fP\&.
.sp
\fI\%AUTOGEN_PARALLEL\fP:
This target property controls the number of \fBmoc\fP or \fBuic\fP processes to
start in parallel during builds.
.sp
\fI\%AUTOGEN_COMMAND_LINE_LENGTH_MAX\fP:
This target property controls the limit when to use response files for
\fBmoc\fP or \fBuic\fP processes on Windows.
.sp
See the \fI\%cmake\-qt(7)\fP manual for more information on using CMake
with Qt.
.SS AUTOMOC_COMPILER_PREDEFINES
.sp
Added in version 3.10.

.sp
Boolean value used by \fI\%AUTOMOC\fP to determine if the
compiler pre definitions file \fBmoc_predefs.h\fP should be generated.
.sp
CMake generates a \fBmoc_predefs.h\fP file with compiler pre definitions
from the output of the command defined in
\fI\%CMAKE_CXX_COMPILER_PREDEFINES_COMMAND\fP
when
.INDENT 0.0
.IP \(bu 2
\fI\%AUTOMOC\fP is enabled,
.IP \(bu 2
\fBAUTOMOC_COMPILER_PREDEFINES\fP is enabled,
.IP \(bu 2
\fI\%CMAKE_CXX_COMPILER_PREDEFINES_COMMAND\fP isn\(aqt empty and
.IP \(bu 2
the Qt version is greater or equal 5.8.
.UNINDENT
.sp
The \fBmoc_predefs.h\fP file, which is generated in \fI\%AUTOGEN_BUILD_DIR\fP,
is passed to \fBmoc\fP as the argument to the \fB\-\-include\fP option.
.sp
By default \fBAUTOMOC_COMPILER_PREDEFINES\fP is initialized from
\fI\%CMAKE_AUTOMOC_COMPILER_PREDEFINES\fP, which is ON by default.
.sp
See the \fI\%cmake\-qt(7)\fP manual for more information on using CMake
with Qt.
.SS AUTOMOC_DEPEND_FILTERS
.sp
Added in version 3.9.

.sp
Filter definitions used by \fI\%AUTOMOC\fP to extract file names from a
source file that are registered as additional dependencies for the
\fBmoc\fP file of the source file.
.sp
Filters are defined as \fBKEYWORD;REGULAR_EXPRESSION\fP pairs. First the file
content is searched for \fBKEYWORD\fP\&. If it is found at least once, then file
names are extracted by successively searching for \fBREGULAR_EXPRESSION\fP and
taking the first match group.
.sp
The file name found in the first match group is searched for
.INDENT 0.0
.IP \(bu 2
first in the vicinity of the source file
.IP \(bu 2
and afterwards in the target\(aqs \fI\%INCLUDE_DIRECTORIES\fP\&.
.UNINDENT
.sp
If any of the extracted files changes, then the \fBmoc\fP file for the source
file gets rebuilt even when the source file itself doesn\(aqt change.
.sp
If any of the extracted files is \fI\%GENERATED\fP or if it is not in the
target\(aqs sources, then it might be necessary to add it to the
\fI\%The <ORIGIN>_autogen target\fP target  dependencies.
See \fI\%AUTOGEN_TARGET_DEPENDS\fP for reference.
.sp
By default \fBAUTOMOC_DEPEND_FILTERS\fP is initialized from
\fI\%CMAKE_AUTOMOC_DEPEND_FILTERS\fP, which is empty by default.
.sp
From Qt 5.15.0 on this variable is ignored as \fBmoc\fP is able to output the
correct dependencies.
.sp
See the \fI\%cmake\-qt(7)\fP manual for more information on using CMake
with Qt.
.SS Example 1
.sp
A header file \fBmy_class.hpp\fP uses a custom macro \fBJSON_FILE_MACRO\fP which
is defined in an other header \fBmacros.hpp\fP\&.
We want the \fBmoc\fP file of \fBmy_class.hpp\fP to depend on the file name
argument of \fBJSON_FILE_MACRO\fP:
.INDENT 0.0
.INDENT 3.5
.sp
.EX
// my_class.hpp
class My_Class : public QObject
{
  Q_OBJECT
  JSON_FILE_MACRO ( \(dqinfo.json\(dq )
\&...
};
.EE
.UNINDENT
.UNINDENT
.sp
In \fBCMakeLists.txt\fP we add a filter to
\fI\%CMAKE_AUTOMOC_DEPEND_FILTERS\fP like this:
.INDENT 0.0
.INDENT 3.5
.sp
.EX
list(APPEND CMAKE_AUTOMOC_DEPEND_FILTERS
  \(dqJSON_FILE_MACRO\(dq
  \(dq[\en][ \et]*JSON_FILE_MACRO[ \et]*\e\e([ \et]*\e\(dq([^\e\(dq]+)\e\(dq\(dq
)
.EE
.UNINDENT
.UNINDENT
.sp
We assume \fBinfo.json\fP is a plain (not \fI\%GENERATED\fP) file that is
listed in the target\(aqs source.  Therefore we do not need to add it to
\fI\%AUTOGEN_TARGET_DEPENDS\fP\&.
.SS Example 2
.sp
In the target \fBmy_target\fP a header file \fBcomplex_class.hpp\fP uses a
custom macro \fBJSON_BASED_CLASS\fP which is defined in an other header
\fBmacros.hpp\fP:
.INDENT 0.0
.INDENT 3.5
.sp
.EX
// macros.hpp
\&...
#define JSON_BASED_CLASS(name, json) \e
class name : public QObject \e
{ \e
  Q_OBJECT \e
  Q_PLUGIN_METADATA(IID \(dqdemo\(dq FILE json) \e
  name() {} \e
};
\&...
.EE
.UNINDENT
.UNINDENT
.INDENT 0.0
.INDENT 3.5
.sp
.EX
// complex_class.hpp
#pragma once
JSON_BASED_CLASS(Complex_Class, \(dqmeta.json\(dq)
// end of file
.EE
.UNINDENT
.UNINDENT
.sp
Since \fBcomplex_class.hpp\fP doesn\(aqt contain a \fBQ_OBJECT\fP macro it would be
ignored by \fI\%AUTOMOC\fP\&.  We change this by adding \fBJSON_BASED_CLASS\fP
to \fI\%CMAKE_AUTOMOC_MACRO_NAMES\fP:
.INDENT 0.0
.INDENT 3.5
.sp
.EX
list(APPEND CMAKE_AUTOMOC_MACRO_NAMES \(dqJSON_BASED_CLASS\(dq)
.EE
.UNINDENT
.UNINDENT
.sp
We want the \fBmoc\fP file of \fBcomplex_class.hpp\fP to depend on
\fBmeta.json\fP\&.  So we add a filter to
\fI\%CMAKE_AUTOMOC_DEPEND_FILTERS\fP:
.INDENT 0.0
.INDENT 3.5
.sp
.EX
list(APPEND CMAKE_AUTOMOC_DEPEND_FILTERS
  \(dqJSON_BASED_CLASS\(dq
  \(dq[\en^][ \et]*JSON_BASED_CLASS[ \et]*\e\e([^,]*,[ \et]*\e\(dq([^\e\(dq]+)\e\(dq\(dq
)
.EE
.UNINDENT
.UNINDENT
.sp
Additionally we assume \fBmeta.json\fP is \fI\%GENERATED\fP which is
why we have to add it to \fI\%AUTOGEN_TARGET_DEPENDS\fP:
.INDENT 0.0
.INDENT 3.5
.sp
.EX
set_property(TARGET my_target APPEND PROPERTY AUTOGEN_TARGET_DEPENDS \(dqmeta.json\(dq)
.EE
.UNINDENT
.UNINDENT
.SS AUTOMOC_EXECUTABLE
.sp
Added in version 3.14.

.sp
\fBAUTOMOC_EXECUTABLE\fP is file path pointing to the \fBmoc\fP
executable to use for \fI\%AUTOMOC\fP enabled files. Setting
this property will make CMake skip the automatic detection of the
\fBmoc\fP binary as well as the sanity\-tests normally run to ensure
that the binary is available and working as expected.
.sp
Usually this property does not need to be set. Only consider this
property if auto\-detection of \fBmoc\fP can not work \-\- e.g. because
you are building the \fBmoc\fP binary as part of your project.
.sp
See the \fI\%cmake\-qt(7)\fP manual for more information on using CMake
with Qt.
.SS AUTOMOC_INCLUDE_DIRECTORIES
.sp
Added in version 4.1.

.sp
Specifies zero or more include directories for AUTOMOC to pass explicitly to
the Qt Meta‑Object Compiler (\fBmoc\fP) instead of automatically discovering a
target\(aqs include directories.
.sp
When this property is set on a target, only the directories listed here will be
used by \fI\%AUTOMOC\fP, and any other include paths will be ignored.
.sp
This property may contain \fI\%generator expressions\fP\&.
.sp
All directory paths in the final evaluated result \fBmust be absolute\fP\&. If any
non\-absolute paths are present after generator expression evaluation,
configuration will fail with an error.
.sp
See also the \fI\%CMAKE_AUTOMOC_INCLUDE_DIRECTORIES\fP variable, which can
be used to initialize this property on all targets.
.SS Example
.INDENT 0.0
.INDENT 3.5
.sp
.EX
add_library(myQtLib ...)
set_property(TARGET myQtLib PROPERTY AUTOMOC_INCLUDE_DIRECTORIES
  \(dq${CMAKE_CURRENT_SOURCE_DIR}/include/myQtLib\(dq
)
.EE
.UNINDENT
.UNINDENT
.SS AUTOMOC_MACRO_NAMES
.sp
Added in version 3.10.

.sp
A \fI\%semicolon\-separated list\fP of macro names used by
\fI\%AUTOMOC\fP to determine if a C++ file needs to be processed by \fBmoc\fP\&.
.sp
This property is only used if the \fI\%AUTOMOC\fP property is \fBON\fP
for this target.
.sp
When running \fI\%AUTOMOC\fP, CMake searches for the strings listed in
\fBAUTOMOC_MACRO_NAMES\fP in C++ source and header files.
If any of the strings is found
.INDENT 0.0
.IP \(bu 2
as the first non space string on a new line or
.IP \(bu 2
as the first non space string after a \fB{\fP on a new line,
.UNINDENT
.sp
then the file will be processed by \fBmoc\fP\&.
.sp
By default \fBAUTOMOC_MACRO_NAMES\fP is initialized from
\fI\%CMAKE_AUTOMOC_MACRO_NAMES\fP\&.
.sp
See also the \fI\%INTERFACE_AUTOMOC_MACRO_NAMES\fP target property.
.sp
See the \fI\%cmake\-qt(7)\fP manual for more information on using CMake
with Qt.
.SS Example
.sp
In this case the \fBQ_OBJECT\fP macro is hidden inside another macro
called \fBCUSTOM_MACRO\fP\&.  To let CMake know that source files that contain
\fBCUSTOM_MACRO\fP need to be \fBmoc\fP processed, we call:
.INDENT 0.0
.INDENT 3.5
.sp
.EX
set_property(TARGET tgt APPEND PROPERTY AUTOMOC_MACRO_NAMES \(dqCUSTOM_MACRO\(dq)
.EE
.UNINDENT
.UNINDENT
.SS AUTOMOC_MOC_OPTIONS
.sp
Additional options for \fBmoc\fP when using \fI\%AUTOMOC\fP
.sp
This property is only used if the \fI\%AUTOMOC\fP property is \fBON\fP
for this target.  In this case, it holds additional command line
options which will be used when \fBmoc\fP is executed during the build, i.e.
it is equivalent to the optional \fBOPTIONS\fP argument of the
\fI\%qt4_wrap_cpp()\fP macro.
.sp
This property is initialized by the value of the
\fI\%CMAKE_AUTOMOC_MOC_OPTIONS\fP variable if it is set when a target
is created, or an empty string otherwise.
.sp
See the \fI\%cmake\-qt(7)\fP manual for more information on using CMake
with Qt.
.SS EXAMPLE
.sp
In this example, the \fBmoc\fP tool is invoked with the \fB\-D_EXTRA_DEFINE\fP
option when generating the moc file for \fBobject.cpp\fP\&.
.INDENT 0.0
.TP
.B \fBCMakeLists.txt\fP
.INDENT 7.0
.INDENT 3.5
.sp
.EX
add_executable(mocOptions object.cpp main.cpp)
set_property(TARGET mocOptions PROPERTY AUTOMOC ON)
target_compile_options(mocOptions PRIVATE \(dq\-D_EXTRA_DEFINE\(dq)
set_property(TARGET mocOptions PROPERTY AUTOMOC_MOC_OPTIONS \(dq\-D_EXTRA_DEFINE\(dq)
target_link_libraries(mocOptions Qt6::Core)
.EE
.UNINDENT
.UNINDENT
.TP
.B \fBobject.hpp\fP
.INDENT 7.0
.INDENT 3.5
.sp
.EX
#ifndef Object_HPP
#define Object_HPP

#include <QObject>

#ifdef _EXTRA_DEFINE
class Object : public QObject
{
Q_OBJECT
public:

  Object();

};
#endif

#endif
.EE
.UNINDENT
.UNINDENT
.UNINDENT
.SS AUTOMOC_PATH_PREFIX
.sp
Added in version 3.16.

.sp
When this property is \fBON\fP, CMake will generate the \fB\-p\fP path prefix
option for \fBmoc\fP on \fI\%AUTOMOC\fP enabled Qt targets.
.sp
To generate the path prefix, CMake tests if the header compiled by \fBmoc\fP
is in any of the target
\fI\%include directories\fP\&.  If so, CMake will
compute the relative path accordingly.  If the header is not in the
\fI\%include directories\fP, CMake will omit
the \fB\-p\fP path prefix option.  \fBmoc\fP usually generates a
relative include path in that case.
.sp
\fBAUTOMOC_PATH_PREFIX\fP is initialized from the variable
\fI\%CMAKE_AUTOMOC_PATH_PREFIX\fP, which is \fBOFF\fP by default.
.sp
See the \fI\%cmake\-qt(7)\fP manual for more information on using CMake
with Qt.
.SS Reproducible builds
.sp
For reproducible builds it is recommended to keep headers that are \fBmoc\fP
compiled in one of the target
\fI\%include directories\fP and set
\fBAUTOMOC_PATH_PREFIX\fP to \fBON\fP\&.  This ensures that:
.INDENT 0.0
.IP \(bu 2
\fBmoc\fP output files are identical on different build setups,
.IP \(bu 2
\fBmoc\fP output files will compile correctly when the source and/or
build directory is a symbolic link.
.UNINDENT
.SS AUTORCC
.sp
Should the target be processed with auto\-rcc (for Qt projects).
.sp
\fBAUTORCC\fP is a boolean specifying whether CMake will handle
the Qt \fBrcc\fP code generator automatically, i.e. without having to use
commands like \fI\%qt4_add_resources()\fP, \X'tty: link https://doc.qt.io/archives/qt-5.15/qtcore-cmake-qt5-add-resources.html'\fI\%qt5_add_resources()\fP\X'tty: link',
etc.  Currently, Qt versions 4 to 6 are supported.
.sp
When this property is \fBON\fP, CMake will handle \fB\&.qrc\fP files added
as target sources at build time and invoke \fBrcc\fP accordingly.
This property is initialized by the value of the \fI\%CMAKE_AUTORCC\fP
variable if it is set when a target is created.
.sp
By default \fBAUTORCC\fP is processed by a
\fI\%custom command\fP\&.
If the \fB\&.qrc\fP file is \fI\%GENERATED\fP, a
\fI\%custom target\fP is used instead.
.sp
When there are multiple \fB\&.qrc\fP files with the same name, CMake will
generate unspecified unique output file names for \fBrcc\fP\&.  Therefore, if
\fBQ_INIT_RESOURCE()\fP or \fBQ_CLEANUP_RESOURCE()\fP need to be used, the
\fB\&.qrc\fP file name must be unique.
.SS Modifiers
.sp
\fI\%AUTORCC_EXECUTABLE\fP:
The \fBrcc\fP executable will be detected automatically, but can be forced to
a certain binary by setting this target property.
.sp
\fI\%AUTORCC_OPTIONS\fP:
Additional command line options for \fBrcc\fP can be set via this target
property.  The corresponding \fI\%AUTORCC_OPTIONS\fP source file property
can be used to specify options to be applied only to a specific \fB\&.qrc\fP file.
.sp
\fI\%SKIP_AUTORCC\fP:
\fB\&.qrc\fP files can be excluded from \fBAUTORCC\fP processing by
setting this source file property.
.sp
\fI\%SKIP_AUTOGEN\fP:
Source files can be excluded from \fI\%AUTOMOC\fP,
\fI\%AUTOUIC\fP and \fBAUTORCC\fP processing by
setting this source file property.
.sp
\fI\%AUTOGEN_SOURCE_GROUP\fP:
This global property can be used to group files generated by
\fI\%AUTOMOC\fP or \fBAUTORCC\fP together in an IDE, e.g.  in MSVS.
.sp
\fI\%AUTOGEN_TARGETS_FOLDER\fP:
This global property can be used to group \fI\%AUTOMOC\fP,
\fI\%AUTOUIC\fP and \fBAUTORCC\fP targets together in an IDE,
e.g.  in MSVS.
.sp
\fI\%CMAKE_GLOBAL_AUTORCC_TARGET\fP:
A global \fBautorcc\fP target that depends on all \fBAUTORCC\fP targets
in the project will be generated when this variable is \fBON\fP\&.
.sp
See the \fI\%cmake\-qt(7)\fP manual for more information on using CMake
with Qt.
.SS AUTORCC_EXECUTABLE
.sp
Added in version 3.14.

.sp
\fBAUTORCC_EXECUTABLE\fP is file path pointing to the \fBrcc\fP
executable to use for \fI\%AUTORCC\fP enabled files. Setting
this property will make CMake skip the automatic detection of the
\fBrcc\fP binary as well as the sanity\-tests normally run to ensure
that the binary is available and working as expected.
.sp
Usually this property does not need to be set. Only consider this
property if auto\-detection of \fBrcc\fP can not work \-\- e.g. because
you are building the \fBrcc\fP binary as part of your project.
.sp
See the \fI\%cmake\-qt(7)\fP manual for more information on using CMake
with Qt.
.SS AUTORCC_OPTIONS
.sp
Additional options for \fBrcc\fP when using \fI\%AUTORCC\fP
.sp
This property holds additional command line options which will be used
when \fBrcc\fP is executed during the build via \fI\%AUTORCC\fP,
i.e. it is equivalent to the optional \fBOPTIONS\fP argument of the
\fI\%qt4_add_resources()\fP macro.
.sp
This property is initialized by the value of the
\fI\%CMAKE_AUTORCC_OPTIONS\fP variable if it is set when a target is
created, or an empty string otherwise.
.sp
The options set on the target may be overridden by \fI\%AUTORCC_OPTIONS\fP
set on the \fB\&.qrc\fP source file.
.sp
See the \fI\%cmake\-qt(7)\fP manual for more information on using CMake
with Qt.
.SS EXAMPLE
.INDENT 0.0
.INDENT 3.5
.sp
.EX
# ...
set_property(TARGET tgt PROPERTY AUTORCC_OPTIONS \(dq\-\-compress;9\(dq)
# ...
.EE
.UNINDENT
.UNINDENT
.SS AUTOUIC
.sp
Should the target be processed with auto\-uic (for Qt projects).
.sp
\fBAUTOUIC\fP is a boolean specifying whether CMake will handle
the Qt \fBuic\fP code generator automatically, i.e. without having to use
commands like \fI\%qt4_wrap_ui()\fP, \X'tty: link https://doc.qt.io/archives/qt-5.15/qtwidgets-cmake-qt5-wrap-ui.html'\fI\%qt5_wrap_ui()\fP\X'tty: link', etc.
Currently, Qt versions 4 to 6 are supported.
.sp
This property is initialized by the value of the \fI\%CMAKE_AUTOUIC\fP
variable if it is set when a target is created.
.sp
When this property is \fBON\fP, CMake will scan the header and source files at
build time and invoke \fBuic\fP accordingly.
.SS Header and source file processing
.sp
At build time, CMake scans each header and source file from the
target\(aqs sources for include statements of the form
.INDENT 0.0
.INDENT 3.5
.sp
.EX
#include \(dqui_<ui_base>.h\(dq
.EE
.UNINDENT
.UNINDENT
.sp
Once such an include statement is found in a file, CMake searches for the
\fBuic\fP input file \fB<ui_base>.ui\fP
.INDENT 0.0
.IP \(bu 2
in the vicinity of the file and
.IP \(bu 2
in the \fI\%AUTOUIC_SEARCH_PATHS\fP of the target.
.UNINDENT
.sp
If the \fB<ui_base>.ui\fP file was found, \fBuic\fP is called on it to generate
\fBui_<ui_base>.h\fP in the directory
.INDENT 0.0
.IP \(bu 2
\fB<AUTOGEN_BUILD_DIR>/include\fP for single configuration generators or in
.IP \(bu 2
\fB<AUTOGEN_BUILD_DIR>/include_<CONFIG>\fP for
\fI\%multi configuration\fP generators.
.UNINDENT
.sp
Where \fB<AUTOGEN_BUILD_DIR>\fP is the value of the target property
\fI\%AUTOGEN_BUILD_DIR\fP\&.
.sp
The include directory is automatically added to the target\(aqs
\fI\%INCLUDE_DIRECTORIES\fP\&.
.SS Modifiers
.sp
\fI\%AUTOUIC_EXECUTABLE\fP:
The \fBuic\fP executable will be detected automatically, but can be forced to
a certain binary using this target property.
.sp
\fI\%AUTOUIC_OPTIONS\fP:
Additional command line options for \fBuic\fP can be set via this target
property.  The corresponding \fI\%AUTOUIC_OPTIONS\fP source file property
can be used to specify options to be applied only to a specific
\fB<base_name>.ui\fP file.
.sp
\fI\%SKIP_AUTOUIC\fP:
Source files can be excluded from \fBAUTOUIC\fP processing by setting
this source file property.
.sp
\fI\%SKIP_AUTOGEN\fP:
Source files can be excluded from \fI\%AUTOMOC\fP,
\fBAUTOUIC\fP and \fI\%AUTORCC\fP processing by
setting this source file property.
.sp
\fI\%AUTOGEN_TARGETS_FOLDER\fP:
This global property can be used to group \fI\%AUTOMOC\fP,
\fBAUTOUIC\fP and \fI\%AUTORCC\fP targets together in an IDE,
e.g.  in MSVS.
.sp
\fI\%CMAKE_GLOBAL_AUTOGEN_TARGET\fP:
A global \fBautogen\fP target, that depends on all \fI\%AUTOMOC\fP or
\fBAUTOUIC\fP generated \fI\%The <ORIGIN>_autogen target\fP targets in the project,
will be generated when this variable is \fBON\fP\&.
.sp
\fI\%AUTOGEN_PARALLEL\fP:
This target property controls the number of \fBmoc\fP or \fBuic\fP processes to
start in parallel during builds.
.sp
\fI\%AUTOGEN_COMMAND_LINE_LENGTH_MAX\fP:
This target property controls the limit when to use response files for
\fBmoc\fP or \fBuic\fP processes on Windows.
.sp
See the \fI\%cmake\-qt(7)\fP manual for more information on using CMake
with Qt.
.SS AUTOUIC_EXECUTABLE
.sp
Added in version 3.14.

.sp
\fBAUTOUIC_EXECUTABLE\fP is file path pointing to the \fBuic\fP
executable to use for \fI\%AUTOUIC\fP enabled files. Setting
this property will make CMake skip the automatic detection of the
\fBuic\fP binary as well as the sanity\-tests normally run to ensure
that the binary is available and working as expected.
.sp
Usually this property does not need to be set. Only consider this
property if auto\-detection of \fBuic\fP can not work \-\- e.g. because
you are building the \fBuic\fP binary as part of your project.
.sp
See the \fI\%cmake\-qt(7)\fP manual for more information on using CMake
with Qt.
.SS AUTOUIC_OPTIONS
.sp
Added in version 3.0.

.sp
Additional options for \fBuic\fP when using \fI\%AUTOUIC\fP
.sp
This property holds additional command line options which will be used when
\fBuic\fP is executed during the build via \fI\%AUTOUIC\fP, i.e. it is
equivalent to the optional \fBOPTIONS\fP argument of the
\fI\%qt4_wrap_ui()\fP macro.
.sp
This property is initialized by the value of the
\fI\%CMAKE_AUTOUIC_OPTIONS\fP variable if it is set when a target is
created, or an empty string otherwise.
.sp
The options set on the target may be overridden by \fI\%AUTOUIC_OPTIONS\fP
set on the \fB\&.ui\fP source file.
.sp
This property may use \(dqgenerator expressions\(dq with the syntax \fB$<...>\fP\&.
See the \fI\%cmake\-generator\-expressions(7)\fP manual for available
expressions.
.sp
See the \fI\%cmake\-qt(7)\fP manual for more information on using CMake
with Qt.
.SS EXAMPLE
.INDENT 0.0
.INDENT 3.5
.sp
.EX
# ...
set_property(TARGET tgt PROPERTY AUTOUIC_OPTIONS \(dq\-\-no\-protection\(dq)
# ...
.EE
.UNINDENT
.UNINDENT
.SS AUTOUIC_SEARCH_PATHS
.sp
Added in version 3.9.

.sp
Search path list used by \fI\%AUTOUIC\fP to find included
\fB\&.ui\fP files.
.sp
This property is initialized by the value of the
\fI\%CMAKE_AUTOUIC_SEARCH_PATHS\fP variable if it is set
when a target is created. Otherwise it is empty.
.sp
See the \fI\%cmake\-qt(7)\fP manual for more information on using CMake
with Qt.
.SS BINARY_DIR
.sp
Added in version 3.4.

.sp
This read\-only property reports the value of the
\fI\%CMAKE_CURRENT_BINARY_DIR\fP variable in the directory in which
the target was defined.
.SS BUILD_RPATH
.sp
Added in version 3.8.

.sp
A \fI\%semicolon\-separated list\fP specifying
runtime path (\fBRPATH\fP) entries to add to binaries linked in the
build tree (for platforms that support it).  By default, CMake sets
the runtime path of binaries in the build tree to contain search
paths it knows are needed to find the shared libraries they link.
Projects may set \fBBUILD_RPATH\fP to specify additional search paths.
.sp
The build\-tree runtime path will \fInot\fP be used for binaries in the
install tree.  It will be replaced with the install\-tree runtime path
during the installation step.  See also the \fI\%INSTALL_RPATH\fP
target property.
.sp
This property is initialized by the value of the variable
\fI\%CMAKE_BUILD_RPATH\fP if it is set when a target is created.
.sp
This property supports
\fI\%generator expressions\fP\&.
.sp
Other settings that affect the build\-tree runtime path include:
.INDENT 0.0
.IP \(bu 2
The \fI\%CMAKE_SKIP_RPATH\fP variable completely disables runtime
paths in both the build tree and install tree.
.IP \(bu 2
The \fI\%SKIP_BUILD_RPATH\fP target property disables setting any
runtime path in the build tree.
.IP \(bu 2
The \fI\%BUILD_RPATH_USE_ORIGIN\fP target property causes the
automatically\-generated runtime path to use entries relative to \fB$ORIGIN\fP\&.
.IP \(bu 2
The \fI\%BUILD_WITH_INSTALL_RPATH\fP target property causes binaries
in the build tree to be built with the install\-tree runtime path.
.UNINDENT
.SS BUILD_RPATH_USE_ORIGIN
.sp
Added in version 3.14.

.sp
Whether to use relative paths for the build \fBRPATH\fP\&.
.sp
This property is initialized by the value of the variable
\fI\%CMAKE_BUILD_RPATH_USE_ORIGIN\fP\&.
.sp
On platforms that support runtime paths (\fBRPATH\fP) with the
\fB$ORIGIN\fP token, setting this property to \fBTRUE\fP enables relative
paths in the build \fBRPATH\fP for executables and shared libraries that
point to shared libraries in the same build tree.
.sp
Normally the build \fBRPATH\fP of a binary contains absolute paths
to the directory of each shared library it links to.  The \fBRPATH\fP
entries for directories contained within the build tree can be made
relative to enable relocatable builds and to help achieve reproducible
builds by omitting the build directory from the build environment.
.sp
This property has no effect on platforms that do not support the
\fB$ORIGIN\fP token in \fBRPATH\fP, or when the \fI\%CMAKE_SKIP_RPATH\fP
variable is set. The runtime path set through the
\fI\%BUILD_RPATH\fP target property is also unaffected by this
property.
.SS BUILD_WITH_INSTALL_NAME_DIR
.sp
Added in version 3.9.

.sp
\fBBUILD_WITH_INSTALL_NAME_DIR\fP is a boolean specifying whether the macOS
\fBinstall_name\fP of a target in the build tree uses the directory given by
\fI\%INSTALL_NAME_DIR\fP\&.  This setting only applies to targets on macOS.
.sp
This property is initialized by the value of the variable
\fI\%CMAKE_BUILD_WITH_INSTALL_NAME_DIR\fP if it is set when a target is
created.
.sp
If this property is not set and policy \fI\%CMP0068\fP is not \fBNEW\fP, the
value of \fI\%BUILD_WITH_INSTALL_RPATH\fP is used in its place.
.SS BUILD_WITH_INSTALL_RPATH
.sp
\fBBUILD_WITH_INSTALL_RPATH\fP is a boolean specifying whether to link the target
in the build tree with the \fI\%INSTALL_RPATH\fP\&.  This takes precedence
over \fI\%SKIP_BUILD_RPATH\fP and avoids the need for relinking before
installation.
.sp
This property is initialized by the value of the
\fI\%CMAKE_BUILD_WITH_INSTALL_RPATH\fP variable if it is set when a target
is created.
.sp
If policy \fI\%CMP0068\fP is not \fBNEW\fP, this property also controls use of
\fI\%INSTALL_NAME_DIR\fP in the build tree on macOS.  Either way, the
\fI\%BUILD_WITH_INSTALL_NAME_DIR\fP target property takes precedence.
.SS BUNDLE
.sp
This target is a \fBCFBundle\fP on the macOS.
.sp
If a module library target has this property set to true it will be
built as a \fBCFBundle\fP when built on the mac.  It will have the directory
structure required for a \fBCFBundle\fP and will be suitable to be used for
creating Browser Plugins or other application resources.
.SS BUNDLE_EXTENSION
.sp
The file extension used to name a \fI\%BUNDLE\fP, a \fI\%FRAMEWORK\fP,
or a \fI\%MACOSX_BUNDLE\fP target on the macOS and iOS.
.sp
The default value is \fBbundle\fP, \fBframework\fP, or \fBapp\fP for the respective
target types.
.SS C_EXTENSIONS
.sp
Added in version 3.1.

.sp
Boolean specifying whether compiler specific extensions are requested.
.sp
This property specifies whether compiler specific extensions should be
used.  For some compilers, this results in adding a flag such
as \fB\-std=gnu11\fP instead of \fB\-std=c11\fP to the compile line.  This
property is \fBON\fP by default. The basic C standard level is
controlled by the \fI\%C_STANDARD\fP target property.
.sp
See the \fI\%cmake\-compile\-features(7)\fP manual for information on
compile features and a list of supported compilers.
.sp
This property is initialized by the value of
the \fI\%CMAKE_C_EXTENSIONS\fP variable if set when a target is created and
otherwise by the value of
\fI\%CMAKE_C_EXTENSIONS_DEFAULT\fP (see
\fI\%CMP0128\fP).
.SS C_STANDARD
.sp
Added in version 3.1.

.sp
The C standard whose features are requested to build this target.
.sp
This property specifies the C standard whose features are requested
to build this target.  For some compilers, this results in adding a
flag such as \fB\-std=gnu11\fP to the compile line.  For compilers that
have no notion of a C standard level, such as Microsoft Visual C++ before
VS 16.7, this property has no effect.
.sp
Supported values are:
.INDENT 0.0
.TP
.B \fB90\fP
C89/C90
.TP
.B \fB99\fP
C99
.TP
.B \fB11\fP
C11
.TP
.B \fB17\fP
Added in version 3.21.

.sp
C17
.TP
.B \fB23\fP
Added in version 3.21.

.sp
C23
.UNINDENT
.sp
If the value requested does not result in a compile flag being added for
the compiler in use, a previous standard flag will be added instead.  This
means that using:
.INDENT 0.0
.INDENT 3.5
.sp
.EX
set_property(TARGET tgt PROPERTY C_STANDARD 11)
.EE
.UNINDENT
.UNINDENT
.sp
with a compiler which does not support \fB\-std=gnu11\fP or an equivalent
flag will not result in an error or warning, but will instead add the
\fB\-std=gnu99\fP or \fB\-std=gnu90\fP flag if supported.  This \(dqdecay\(dq behavior may
be controlled with the \fI\%C_STANDARD_REQUIRED\fP target property.
Additionally, the \fI\%C_EXTENSIONS\fP target property may be used to
control whether compiler\-specific extensions are enabled on a per\-target basis.
.sp
See the \fI\%cmake\-compile\-features(7)\fP manual for information on
compile features and a list of supported compilers.
.sp
This property is initialized by the value of
the \fI\%CMAKE_C_STANDARD\fP variable if it is set when a target
is created.
.SS C_STANDARD_REQUIRED
.sp
Added in version 3.1.

.sp
Boolean describing whether the value of \fI\%C_STANDARD\fP is a requirement.
.sp
If this property is set to \fBON\fP, then the value of the
\fI\%C_STANDARD\fP target property is treated as a requirement.  If this
property is \fBOFF\fP or unset, the \fI\%C_STANDARD\fP target property is
treated as optional and may \(dqdecay\(dq to a previous standard if the requested is
not available.  For compilers that have no notion of a C standard level, such
as Microsoft Visual C++ before VS 16.7, this property has no effect.
.sp
See the \fI\%cmake\-compile\-features(7)\fP manual for information on
compile features and a list of supported compilers.
.sp
This property is initialized by the value of
the \fI\%CMAKE_C_STANDARD_REQUIRED\fP variable if it is set when a
target is created.
.SS COMMON_LANGUAGE_RUNTIME
.sp
Added in version 3.12.

.sp
By setting this target property, the target is configured to build with
\fBC++/CLI\fP support.
.sp
The \fI\%Visual Studio Generators\fP define the \fBclr\fP parameter depending on
the value of the \fBCOMMON_LANGUAGE_RUNTIME\fP target property:
.sp
Not Set (default)
.INDENT 0.0
.INDENT 3.5
Native C++.
.UNINDENT
.UNINDENT
.sp
\fB\(dq\(dq\fP (set but empty)
.INDENT 0.0
.INDENT 3.5
Mixed unmanaged/managed C++ using .NET Framework.
.UNINDENT
.UNINDENT
.INDENT 0.0
.TP
.B \fBnetcore\fP
Added in version 3.26.

.sp
Mixed unmanaged/managed C++ using .NET Core.
.sp
This required VS 2019\(aqs v142 toolset or higher.
.UNINDENT
.sp
\fBpure\fP
.INDENT 0.0
.INDENT 3.5
Managed C++.
.UNINDENT
.UNINDENT
.sp
\fBsafe\fP
.INDENT 0.0
.INDENT 3.5
Managed C++.
.UNINDENT
.UNINDENT
.sp
This property is only evaluated \fI\%Visual Studio Generators\fP for
VS 2010 and above.
.sp
To be able to build managed C++ targets with VS 2017 and above the component
\fBC++/CLI support\fP must be installed, which may not be done by default.
.sp
See also \fI\%IMPORTED_COMMON_LANGUAGE_RUNTIME\fP
.SS COMPATIBLE_INTERFACE_BOOL
.sp
Properties which must be compatible with their link interface
.sp
The \fBCOMPATIBLE_INTERFACE_BOOL\fP property may contain a list of
properties for this target which must be consistent when evaluated as a
boolean with the \fBINTERFACE\fP variant of the property in all linked
dependees.  For example, if a property \fBFOO\fP appears in the list, then
for each dependee, the \fBINTERFACE_FOO\fP property content in all of its
dependencies must be consistent with each other, and with the \fBFOO\fP
property in the depender.
.sp
Consistency in this sense has the meaning that if the property is set,
then it must have the same boolean value as all others, and if the
property is not set, then it is ignored.
.sp
Note that for each dependee, the set of properties specified in this
property must not intersect with the set specified in any of the other
\fI\%Compatible Interface Properties\fP\&.
.SS COMPATIBLE_INTERFACE_NUMBER_MAX
.sp
Properties whose maximum value from the link interface will be used.
.sp
The \fBCOMPATIBLE_INTERFACE_NUMBER_MAX\fP property may contain a list of
properties for this target whose maximum value may be read at generate
time when evaluated in the \fBINTERFACE\fP variant of the property in all
linked dependees.  For example, if a property \fBFOO\fP appears in the list,
then for each dependee, the \fBINTERFACE_FOO\fP property content in all of
its dependencies will be compared with each other and with the \fBFOO\fP
property in the depender.  When reading the \fBFOO\fP property at generate
time, the maximum value will be returned. If the property is not set,
then it is ignored.
.sp
Note that for each dependee, the set of properties specified in this
property must not intersect with the set specified in any of the other
\fI\%Compatible Interface Properties\fP\&.
.SS COMPATIBLE_INTERFACE_NUMBER_MIN
.sp
Properties whose minimum value from the link interface will be used.
.sp
The \fBCOMPATIBLE_INTERFACE_NUMBER_MIN\fP property may contain a list of
properties for this target whose minimum value may be read at generate
time when evaluated in the \fBINTERFACE\fP variant of the property of all
linked dependees.  For example, if a
property \fBFOO\fP appears in the list, then for each dependee, the
\fBINTERFACE_FOO\fP property content in all of its dependencies will be
compared with each other and with the \fBFOO\fP property in the depender.
When reading the \fBFOO\fP property at generate time, the minimum value
will be returned.  If the property is not set, then it is ignored.
.sp
Note that for each dependee, the set of properties specified in this
property must not intersect with the set specified in any of the other
\fI\%Compatible Interface Properties\fP\&.
.SS COMPATIBLE_INTERFACE_STRING
.sp
Properties which must be string\-compatible with their link interface
.sp
The \fBCOMPATIBLE_INTERFACE_STRING\fP property may contain a list of
properties for this target which must be the same when evaluated as a
string in the \fBINTERFACE\fP variant of the property all linked dependees.
For example, if a property \fBFOO\fP appears in the list, then for each
dependee, the \fBINTERFACE_FOO\fP property content in all of its
dependencies must be equal with each other, and with the \fBFOO\fP property
in the depender.  If the property is not set, then it is ignored.
.sp
Note that for each dependee, the set of properties specified in this
property must not intersect with the set specified in any of the other
\fI\%Compatible Interface Properties\fP\&.
.SS COMPILE_DEFINITIONS
.sp
Preprocessor definitions for compiling a target\(aqs sources.
.sp
The \fBCOMPILE_DEFINITIONS\fP property may be set to a semicolon\-separated
list of preprocessor definitions using the syntax \fBVAR\fP or \fBVAR=value\fP\&.
Function\-style definitions are not supported.  CMake will
automatically escape the value correctly for the native build system
(note that CMake language syntax may require escapes to specify some
values).
.sp
CMake will automatically drop some definitions that are not supported
by the native build tool.
.sp
Added in version 3.26: Any leading \fB\-D\fP on an item will be removed.

.sp
Disclaimer: Most native build tools have poor support for escaping
certain values.  CMake has work\-arounds for many cases but some values
may just not be possible to pass correctly.  If a value does not seem
to be escaped correctly, do not attempt to work\-around the problem by
adding escape sequences to the value.  Your work\-around may break in a
future version of CMake that has improved escape support.  Instead
consider defining the macro in a (configured) header file.  Then
report the limitation.  Known limitations include:
.INDENT 0.0
.INDENT 3.5
.TS
box center;
l|l.
T{
\fB#\fP
T}	T{
Broken almost everywhere.
T}
_
T{
\fB;\fP
T}	T{
Broken in VS IDE 7.0 and Borland Makefiles.
T}
_
T{
\fB,\fP
T}	T{
Broken in VS IDE.
T}
_
T{
\fB%\fP
T}	T{
Broken in some cases in NMake.
T}
_
T{
\fB& |\fP
T}	T{
Broken in some cases on MinGW.
T}
_
T{
\fB^ < > \e \(dq\fP
T}	T{
Broken in most Make tools on Windows.
T}
.TE
.UNINDENT
.UNINDENT
.sp
CMake does not reject these values outright because they do work in
some cases.  Use with caution.
.sp
Contents of \fBCOMPILE_DEFINITIONS\fP may use \(dqgenerator expressions\(dq with the
syntax \fB$<...>\fP\&.  See the \fI\%cmake\-generator\-expressions(7)\fP manual
for available expressions.  See the \fI\%cmake\-buildsystem(7)\fP manual
for more on defining buildsystem properties.
.sp
The corresponding \fI\%COMPILE_DEFINITIONS_<CONFIG>\fP property may
be set to specify per\-configuration definitions.  Generator expressions
should be preferred instead of setting the alternative property.
.SS COMPILE_FEATURES
.sp
Added in version 3.1.

.sp
Compiler features enabled for this target.
.sp
The list of features in this property are a subset of the features listed
in the \fI\%CMAKE_C_COMPILE_FEATURES\fP, \fI\%CMAKE_CUDA_COMPILE_FEATURES\fP, and
\fI\%CMAKE_CXX_COMPILE_FEATURES\fP variables.
.sp
Contents of \fBCOMPILE_FEATURES\fP may use \(dqgenerator expressions\(dq with the
syntax \fB$<...>\fP\&.  See the \fI\%cmake\-generator\-expressions(7)\fP manual for
available expressions.  See the \fI\%cmake\-compile\-features(7)\fP manual
for information on compile features and a list of supported compilers.
.SS COMPILE_FLAGS
.sp
Additional flags to use when compiling this target\(aqs sources.
.sp
The \fBCOMPILE_FLAGS\fP property sets additional compiler flags used to
build sources within the target.  Use \fI\%COMPILE_DEFINITIONS\fP
to pass additional preprocessor definitions.
.sp
\fBNOTE:\fP
.INDENT 0.0
.INDENT 3.5
This property has been superseded by the \fI\%COMPILE_OPTIONS\fP property.
Alternatively, you can also use the \fI\%target_compile_options()\fP command
instead.
.UNINDENT
.UNINDENT
.SS COMPILE_OPTIONS
.sp
List of options to pass to the compiler.
.sp
This property holds a \fI\%semicolon\-separated list\fP
of options specified so far for its target.  Use the
\fI\%target_compile_options()\fP command to append more options.
The options will be added after flags in the
\fI\%CMAKE_<LANG>_FLAGS\fP and \fI\%CMAKE_<LANG>_FLAGS_<CONFIG>\fP
variables, but before those propagated from dependencies by the
\fI\%INTERFACE_COMPILE_OPTIONS\fP property.
.sp
This property adds compile options for all languages in a target.
Use the \fI\%COMPILE_LANGUAGE\fP generator expression to specify
per\-language compile options.
.sp
This property is initialized by the \fI\%COMPILE_OPTIONS\fP directory
property when a target is created, and is used by the generators to set
the options for the compiler.
.sp
Contents of \fBCOMPILE_OPTIONS\fP may use \(dqgenerator expressions\(dq with the
syntax \fB$<...>\fP\&.  See the \fI\%cmake\-generator\-expressions(7)\fP manual
for available expressions.  See the \fI\%cmake\-buildsystem(7)\fP manual
for more on defining buildsystem properties.
.SS Option De\-duplication
.sp
The final set of options used for a target is constructed by
accumulating options from the current target and the usage requirements of
its dependencies.  The set of options is de\-duplicated to avoid repetition.
.sp
Added in version 3.12: While beneficial for individual options, the de\-duplication step can break
up option groups.  For example, \fB\-option A \-option B\fP becomes
\fB\-option A B\fP\&.  One may specify a group of options using shell\-like
quoting along with a \fBSHELL:\fP prefix.  The \fBSHELL:\fP prefix is dropped,
and the rest of the option string is parsed using the
\fI\%separate_arguments()\fP \fBUNIX_COMMAND\fP mode. For example,
\fB\(dqSHELL:\-option A\(dq \(dqSHELL:\-option B\(dq\fP becomes \fB\-option A \-option B\fP\&.

.SS COMPILE_PDB_NAME
.sp
Added in version 3.1.

.sp
Output name for the MS debug symbol \fB\&.pdb\fP file generated by the
compiler while building source files.
.sp
This property specifies the base name for the debug symbols file.
If not set, the default is unspecified.
.sp
Added in version 4.1: Contents of \fBCOMPILE_PDB_NAME\fP may use
\fI\%generator expressions\fP\&.

.sp
\fBNOTE:\fP
.INDENT 0.0
.INDENT 3.5
The compiler\-generated program database files are specified by the
\fB/Fd\fP compiler flag and are not the same as linker\-generated
program database files specified by the \fB/pdb\fP linker flag.
Use the \fI\%PDB_NAME\fP property to specify the latter.
.UNINDENT
.UNINDENT
.SS COMPILE_PDB_NAME_<CONFIG>
.sp
Added in version 3.1.

.sp
Per\-configuration output name for the MS debug symbol \fB\&.pdb\fP file
generated by the compiler while building source files.
.sp
This is the configuration\-specific version of \fI\%COMPILE_PDB_NAME\fP\&.
.sp
Added in version 4.1: Contents of \fBCOMPILE_PDB_NAME_<CONFIG>\fP may use
\fI\%generator expressions\fP\&.

.sp
\fBNOTE:\fP
.INDENT 0.0
.INDENT 3.5
The compiler\-generated program database files are specified by the
\fB/Fd\fP compiler flag and are not the same as linker\-generated
program database files specified by the \fB/pdb\fP linker flag.
Use the \fI\%PDB_NAME_<CONFIG>\fP property to specify the latter.
.UNINDENT
.UNINDENT
.SS COMPILE_PDB_OUTPUT_DIRECTORY
.sp
Added in version 3.1.

.sp
Output directory for the MS debug symbol \fB\&.pdb\fP file
generated by the compiler while building source files.
.sp
This property specifies the directory into which the MS debug symbols
will be placed by the compiler.
.sp
Added in version 3.12: The property value may use
\fI\%generator expressions\fP\&.
Multi\-configuration generators append a per\-configuration
subdirectory to the specified directory unless a generator expression
is used.

.sp
This property is initialized by the value of the
\fI\%CMAKE_COMPILE_PDB_OUTPUT_DIRECTORY\fP variable if it is
set when a target is created.
.sp
\fBNOTE:\fP
.INDENT 0.0
.INDENT 3.5
The compiler\-generated program database files are specified by the
\fB/Fd\fP compiler flag and are not the same as linker\-generated
program database files specified by the \fB/pdb\fP linker flag.
Use the \fI\%PDB_OUTPUT_DIRECTORY\fP property to specify the latter.
.UNINDENT
.UNINDENT
.SS COMPILE_PDB_OUTPUT_DIRECTORY_<CONFIG>
.sp
Added in version 3.1.

.sp
Per\-configuration output directory for the MS debug symbol \fB\&.pdb\fP file
generated by the compiler while building source files.
.sp
This is a per\-configuration version of
\fI\%COMPILE_PDB_OUTPUT_DIRECTORY\fP,
but multi\-configuration generators (\fI\%Visual Studio\fP, \fI\%Xcode\fP, \fI\%Ninja Multi\-Config\fP) do NOT
append a per\-configuration subdirectory to the specified directory.  This
property is initialized by the value of the
\fI\%CMAKE_COMPILE_PDB_OUTPUT_DIRECTORY_<CONFIG>\fP variable
if it is set when a target is created.
.sp
Added in version 3.12: Contents of \fBCOMPILE_PDB_OUTPUT_DIRECTORY_<CONFIG>\fP may use
\fI\%generator expressions\fP\&.

.sp
\fBNOTE:\fP
.INDENT 0.0
.INDENT 3.5
The compiler\-generated program database files are specified by the
\fB/Fd\fP compiler flag and are not the same as linker\-generated
program database files specified by the \fB/pdb\fP linker flag.
Use the \fI\%PDB_OUTPUT_DIRECTORY_<CONFIG>\fP property to specify the latter.
.UNINDENT
.UNINDENT
.SS COMPILE_WARNING_AS_ERROR
.sp
Added in version 3.24.

.sp
Specify whether to treat warnings on compile as errors.
If enabled, adds a flag to treat warnings on compile as errors.
If the \fI\%cmake \-\-compile\-no\-warning\-as\-error\fP option is given
on the \fI\%cmake(1)\fP command line, this property is ignored.
.sp
This property is not implemented for all compilers.  It is silently ignored
if there is no implementation for the compiler being used.  The currently
implemented \fI\%compiler IDs\fP are:
.INDENT 0.0
.IP \(bu 2
\fBGNU\fP
.IP \(bu 2
\fBClang\fP
.IP \(bu 2
\fBAppleClang\fP
.IP \(bu 2
\fBFujitsu\fP
.IP \(bu 2
\fBFujitsuClang\fP
.IP \(bu 2
\fBIBMClang\fP
.IP \(bu 2
\fBIntel\fP
.IP \(bu 2
\fBIntelLLVM\fP
.IP \(bu 2
\fBLCC\fP
.IP \(bu 2
\fBMSVC\fP
.IP \(bu 2
\fBNVHPC\fP
.IP \(bu 2
\fBNVIDIA\fP (CUDA)
.IP \(bu 2
\fBQCC\fP
.IP \(bu 2
\fBSunPro\fP
.IP \(bu 2
\fBTasking\fP
.IP \(bu 2
\fBTI\fP
.IP \(bu 2
\fBVisualAge\fP
.IP \(bu 2
\fBXL\fP
.IP \(bu 2
\fBXLClang\fP
.UNINDENT
.sp
This property is initialized by the value of the variable
\fI\%CMAKE_COMPILE_WARNING_AS_ERROR\fP if it is set when a target is
created.
.SS <CONFIG>_OUTPUT_NAME
.sp
Old per\-configuration target file base name.
Use \fI\%OUTPUT_NAME_<CONFIG>\fP instead.
.sp
This is a configuration\-specific version of the \fI\%OUTPUT_NAME\fP
target property.
.SS <CONFIG>_POSTFIX
.sp
Postfix to append to the target file name for configuration \fB<CONFIG>\fP\&.
.sp
When building with configuration \fB<CONFIG>\fP the value of this property
is appended to the target file name built on disk.  For non\-executable
targets, this property is initialized by the value of the
\fI\%CMAKE_<CONFIG>_POSTFIX\fP variable if it is set when a target is
created.  This property is ignored on macOS for Frameworks and App Bundles.
.sp
For macOS see also the \fI\%FRAMEWORK_MULTI_CONFIG_POSTFIX_<CONFIG>\fP
target property.
.SS CROSSCOMPILING_EMULATOR
.sp
Added in version 3.3.

.sp
Use the given emulator to run executables created when crosscompiling.
This command will be added as a prefix to \fI\%add_test()\fP,
\fI\%add_custom_command()\fP, and \fI\%add_custom_target()\fP commands
for built target system executables.
.sp
Added in version 3.15: If this property contains a \fI\%semicolon\-separated list\fP, then the first value is the command and remaining values are its
arguments.

.sp
Added in version 3.29: Contents of \fBCROSSCOMPILING_EMULATOR\fP may use
\fI\%generator expressions\fP\&.

.sp
This property is initialized by the value of the
\fI\%CMAKE_CROSSCOMPILING_EMULATOR\fP variable if it is set when a target
is created.
.SS CUDA_ARCHITECTURES
.sp
Added in version 3.18.

.sp
List of architectures to generate device code for.
.sp
An architecture can be suffixed by either \fB\-real\fP or \fB\-virtual\fP to specify
the kind of architecture to generate code for.
If no suffix is given then code is generated for both real and virtual
architectures.
.sp
A non\-empty false value (e.g. \fBOFF\fP) disables adding architectures.
This is intended to support packagers and rare cases where full control
over the passed flags is required.
.sp
This property is initialized by the value of the \fI\%CMAKE_CUDA_ARCHITECTURES\fP
variable if it is set when a target is created.
.sp
The \fBCUDA_ARCHITECTURES\fP target property must be set to a non\-empty value on targets
that compile CUDA sources, or it is an error.  See policy \fI\%CMP0104\fP\&.
.sp
The \fBCUDA_ARCHITECTURES\fP may be set to one of the following special values:
.INDENT 0.0
.TP
.B \fBall\fP
Added in version 3.23.

.sp
Compile for all supported major and minor real architectures,
and the highest major virtual architecture.
.TP
.B \fBall\-major\fP
Added in version 3.23.

.sp
Compile for all supported major real architectures, and the highest
major virtual architecture.
.TP
.B \fBnative\fP
Added in version 3.24.

.sp
Compile for the architecture(s) of the host\(aqs GPU(s).
.UNINDENT
.SS Examples
.INDENT 0.0
.INDENT 3.5
.sp
.EX
set_target_properties(tgt PROPERTIES CUDA_ARCHITECTURES \(dq35;50;72\(dq)
.EE
.UNINDENT
.UNINDENT
.sp
Generates code for real and virtual architectures \fB30\fP, \fB50\fP and \fB72\fP\&.
.INDENT 0.0
.INDENT 3.5
.sp
.EX
set_property(TARGET tgt PROPERTY CUDA_ARCHITECTURES 70\-real 72\-virtual)
.EE
.UNINDENT
.UNINDENT
.sp
Generates code for real architecture \fB70\fP and virtual architecture \fB72\fP\&.
.INDENT 0.0
.INDENT 3.5
.sp
.EX
set_property(TARGET tgt PROPERTY CUDA_ARCHITECTURES OFF)
.EE
.UNINDENT
.UNINDENT
.sp
CMake will not pass any architecture flags to the compiler.
.SS CUDA_CUBIN_COMPILATION
.sp
Added in version 3.27.

.sp
Compile CUDA sources to \fB\&.cubin\fP files instead of \fB\&.obj\fP files
within \fI\%Object Libraries\fP\&.
.sp
For example:
.INDENT 0.0
.INDENT 3.5
.sp
.EX
add_library(mycubin OBJECT a.cu b.cu)
set_property(TARGET mycubin PROPERTY CUDA_CUBIN_COMPILATION ON)
.EE
.UNINDENT
.UNINDENT
.SS CUDA_EXTENSIONS
.sp
Added in version 3.8.

.sp
Boolean specifying whether compiler specific extensions are requested.
.sp
This property specifies whether compiler specific extensions should be
used.  For some compilers, this results in adding a flag such
as \fB\-std=gnu++11\fP instead of \fB\-std=c++11\fP to the compile line.  This
property is \fBON\fP by default. The basic CUDA/C++ standard level is
controlled by the \fI\%CUDA_STANDARD\fP target property.
.sp
See the \fI\%cmake\-compile\-features(7)\fP manual for information on
compile features and a list of supported compilers.
.sp
This property is initialized by the value of
the \fI\%CMAKE_CUDA_EXTENSIONS\fP variable if set when a target is created
and otherwise by the value of
\fI\%CMAKE_CUDA_EXTENSIONS_DEFAULT\fP
(see \fI\%CMP0128\fP).
.SS CUDA_FATBIN_COMPILATION
.sp
Added in version 3.27.

.sp
Compile CUDA sources to \fB\&.fatbin\fP files instead of \fB\&.obj\fP files
within \fI\%Object Libraries\fP\&.
.sp
For example:
.INDENT 0.0
.INDENT 3.5
.sp
.EX
add_library(myfbins OBJECT a.cu b.cu)
set_property(TARGET myfbins PROPERTY CUDA_FATBIN_COMPILATION ON)
.EE
.UNINDENT
.UNINDENT
.SS CUDA_OPTIX_COMPILATION
.sp
Added in version 3.27.

.sp
Compile CUDA sources to \fB\&.optixir\fP files instead of \fB\&.obj\fP files
within \fI\%Object Libraries\fP\&.
.sp
For example:
.INDENT 0.0
.INDENT 3.5
.sp
.EX
add_library(myoptix OBJECT a.cu b.cu)
set_property(TARGET myoptix PROPERTY CUDA_OPTIX_COMPILATION ON)
.EE
.UNINDENT
.UNINDENT
.SS CUDA_PTX_COMPILATION
.sp
Added in version 3.9.

.sp
Compile CUDA sources to \fB\&.ptx\fP files instead of \fB\&.obj\fP files
within \fI\%Object Libraries\fP\&.
.sp
For example:
.INDENT 0.0
.INDENT 3.5
.sp
.EX
add_library(myptx OBJECT a.cu b.cu)
set_property(TARGET myptx PROPERTY CUDA_PTX_COMPILATION ON)
.EE
.UNINDENT
.UNINDENT
.SS CUDA_RESOLVE_DEVICE_SYMBOLS
.sp
Added in version 3.9.

.sp
CUDA only: Enables device linking for the specific library target where
required.
.sp
If set, this will tell the required compilers to enable device linking
on the library target. Device linking is an additional link step
required by some CUDA compilers when \fI\%CUDA_SEPARABLE_COMPILATION\fP is
enabled. Normally device linking is deferred until a shared library or
executable is generated, allowing for multiple static libraries to resolve
device symbols at the same time when they are used by a shared library or
executable.
.sp
If this property or \fI\%CMAKE_CUDA_RESOLVE_DEVICE_SYMBOLS\fP is unset,
static libraries are treated as if it is disabled while shared, module,
and executable targets behave as if it is on.
.sp
If \fI\%CMAKE_CUDA_RESOLVE_DEVICE_SYMBOLS\fP has been defined,
this property is initialized to the value the variable and overriding
the default behavior.
.sp
Note that device linking is not supported for \fI\%Object Libraries\fP\&.
.sp
For instance:
.INDENT 0.0
.INDENT 3.5
.sp
.EX
set_property(TARGET mystaticlib PROPERTY CUDA_RESOLVE_DEVICE_SYMBOLS ON)
.EE
.UNINDENT
.UNINDENT
.SS CUDA_RUNTIME_LIBRARY
.sp
Added in version 3.17.

.sp
Select the CUDA runtime library for use by compilers targeting the CUDA language.
.sp
The allowed case insensitive values are:
.INDENT 0.0
.TP
.B \fBNone\fP
Link with \fB\-cudart=none\fP or equivalent flag(s) to use no CUDA
runtime library.
.TP
.B \fBShared\fP
Link with \fB\-cudart=shared\fP or equivalent flag(s) to use a
dynamically\-linked CUDA runtime library.
.TP
.B \fBStatic\fP
Link with \fB\-cudart=static\fP or equivalent flag(s) to use a
statically\-linked CUDA runtime library.
.UNINDENT
.sp
Contents of \fBCUDA_RUNTIME_LIBRARY\fP may use
\fI\%generator expressions\fP\&.
.sp
If that property is not set then CMake uses an appropriate default
value based on the compiler to select the CUDA runtime library.
.sp
\fBNOTE:\fP
.INDENT 0.0
.INDENT 3.5
This property has effect only when the \fBCUDA\fP language is enabled. To
control the CUDA runtime linking when only using the CUDA SDK with the
\fBC\fP or \fBC++\fP language we recommend using the \fI\%FindCUDAToolkit\fP
module.
.UNINDENT
.UNINDENT
.SS CUDA_SEPARABLE_COMPILATION
.sp
Added in version 3.8.

.sp
CUDA only: Enables separate compilation of device code
.sp
If set this will enable separable compilation for all CUDA files for
the given target.
.sp
For instance:
.INDENT 0.0
.INDENT 3.5
.sp
.EX
set_property(TARGET myexe PROPERTY CUDA_SEPARABLE_COMPILATION ON)
.EE
.UNINDENT
.UNINDENT
.sp
This property is initialized by the value of the
\fI\%CMAKE_CUDA_SEPARABLE_COMPILATION\fP variable if it is set when a
target is created.
.SS CUDA_STANDARD
.sp
Added in version 3.8.

.sp
The CUDA/C++ standard whose features are requested to build this target.
.sp
This property specifies the CUDA/C++ standard whose features are requested
to build this target.  For some compilers, this results in adding a
flag such as \fB\-std=gnu++11\fP to the compile line.
.sp
Supported values are:
.INDENT 0.0
.TP
.B \fB98\fP
CUDA C++98. Note that this maps to the same as \fB03\fP internally.
.TP
.B \fB03\fP
CUDA C++03
.TP
.B \fB11\fP
CUDA C++11
.TP
.B \fB14\fP
CUDA C++14. While CMake 3.8 and later \fIrecognize\fP \fB14\fP as a valid value,
CMake 3.9 was the first version to include support for any compiler.
.TP
.B \fB17\fP
CUDA C++17. While CMake 3.8 and later \fIrecognize\fP \fB17\fP as a valid value,
CMake 3.18 was the first version to include support for any compiler.
.TP
.B \fB20\fP
Added in version 3.12.

.sp
CUDA C++20. While CMake 3.12 and later \fIrecognize\fP \fB20\fP as a valid value,
CMake 3.18 was the first version to include support for any compiler.
.TP
.B \fB23\fP
Added in version 3.20.

.sp
CUDA C++23
.TP
.B \fB26\fP
Added in version 3.25.

.sp
CUDA C++26. CMake 3.25 and later \fIrecognize\fP \fB26\fP as a valid value,
no version has support for any compiler.
.UNINDENT
.sp
If the value requested does not result in a compile flag being added for
the compiler in use, a previous standard flag will be added instead.  This
means that using:
.INDENT 0.0
.INDENT 3.5
.sp
.EX
set_property(TARGET tgt PROPERTY CUDA_STANDARD 11)
.EE
.UNINDENT
.UNINDENT
.sp
with a compiler which does not support \fB\-std=gnu++11\fP or an equivalent
flag will not result in an error or warning, but will instead add the
\fB\-std=gnu++03\fP flag if supported.  This \(dqdecay\(dq behavior may be controlled
with the \fI\%CUDA_STANDARD_REQUIRED\fP target property.
Additionally, the \fI\%CUDA_EXTENSIONS\fP target property may be used to
control whether compiler\-specific extensions are enabled on a per\-target basis.
.sp
See the \fI\%cmake\-compile\-features(7)\fP manual for information on
compile features and a list of supported compilers.
.sp
This property is initialized by the value of
the \fI\%CMAKE_CUDA_STANDARD\fP variable if it is set when a target
is created.
.SS CUDA_STANDARD_REQUIRED
.sp
Added in version 3.8.

.sp
Boolean describing whether the value of \fI\%CUDA_STANDARD\fP is a requirement.
.sp
If this property is set to \fBON\fP, then the value of the
\fI\%CUDA_STANDARD\fP target property is treated as a requirement.  If this
property is \fBOFF\fP or unset, the \fI\%CUDA_STANDARD\fP target property is
treated as optional and may \(dqdecay\(dq to a previous standard if the requested is
not available.  For compilers that have no notion of a standard level, such as
MSVC 1800 (Visual Studio 2013) and lower, this has no effect.
.sp
See the \fI\%cmake\-compile\-features(7)\fP manual for information on
compile features and a list of supported compilers.
.sp
This property is initialized by the value of
the \fI\%CMAKE_CUDA_STANDARD_REQUIRED\fP variable if it is set when a
target is created.
.SS CXX_EXTENSIONS
.sp
Added in version 3.1.

.sp
Boolean specifying whether compiler specific extensions are requested.
.sp
This property specifies whether compiler specific extensions should be
used.  For some compilers, this results in adding a flag such
as \fB\-std=gnu++11\fP instead of \fB\-std=c++11\fP to the compile line.  This
property is \fBON\fP by default. The basic C++ standard level is
controlled by the \fI\%CXX_STANDARD\fP target property.
.sp
See the \fI\%cmake\-compile\-features(7)\fP manual for information on
compile features and a list of supported compilers.
.sp
This property is initialized by the value of
the \fI\%CMAKE_CXX_EXTENSIONS\fP variable if set when a target is created
and otherwise by the value of
\fI\%CMAKE_CXX_EXTENSIONS_DEFAULT\fP (see
\fI\%CMP0128\fP).
.SS CXX_MODULE_DIRS
.sp
Added in version 3.28.

.sp
Semicolon\-separated list of base directories of the target\(aqs default
C++ module set (i.e. the file set with name and type \fBCXX_MODULES\fP). The
property supports
\fI\%generator expressions\fP\&.
.sp
This property is normally only set by \fI\%target_sources(FILE_SET)\fP
rather than being manipulated directly.
.sp
See \fI\%CXX_MODULE_DIRS_<NAME>\fP for the list of base directories in
other C++ module sets.
.SS CXX_MODULE_DIRS_<NAME>
.sp
Added in version 3.28.

.sp
Semicolon\-separated list of base directories of the target\(aqs \fB<NAME>\fP C++
module set, which has the set type \fBCXX_MODULES\fP\&. The property supports
\fI\%generator expressions\fP\&.
.sp
This property is normally only set by \fI\%target_sources(FILE_SET)\fP
rather than being manipulated directly.
.sp
See \fI\%CXX_MODULE_DIRS\fP for the list of base directories in the
default C++ module set. See \fI\%CXX_MODULE_SETS\fP for the file set names
of all C++ module sets.
.SS CXX_MODULE_SET
.sp
Added in version 3.28.

.sp
Semicolon\-separated list of files in the target\(aqs default C++ module set,
(i.e. the file set with name and type \fBCXX_MODULES\fP). If any of the paths
are relative, they are computed relative to the target\(aqs source directory. The
property supports
\fI\%generator expressions\fP\&.
.sp
This property is normally only set by \fI\%target_sources(FILE_SET)\fP
rather than being manipulated directly.
.sp
See \fI\%CXX_MODULE_SET_<NAME>\fP for the list of files in other C++
module sets.
.SS CXX_MODULE_SET_<NAME>
.sp
Added in version 3.28.

.sp
Semicolon\-separated list of files in the target\(aqs \fB<NAME>\fP C++ module set,
which has the set type \fBCXX_MODULES\fP\&. If any of the paths are relative, they
are computed relative to the target\(aqs source directory. The property supports
\fI\%generator expressions\fP\&.
.sp
This property is normally only set by \fI\%target_sources(FILE_SET)\fP
rather than being manipulated directly.
.sp
See \fI\%CXX_MODULE_SET\fP for the list of files in the default C++ module
set. See \fI\%CXX_MODULE_SETS\fP for the file set names of all C++ module
sets.
.SS CXX_MODULE_SETS
.sp
Added in version 3.28.

.sp
Read\-only list of the target\(aqs \fBPRIVATE\fP and \fBPUBLIC\fP C++ module sets (i.e.
all file sets with the type \fBCXX_MODULES\fP). Files listed in these file sets
are treated as source files for the purpose of IDE integration.
.sp
C++ module sets may be defined using the \fI\%target_sources()\fP command
\fBFILE_SET\fP option with type \fBCXX_MODULES\fP\&.
.sp
See also \fI\%CXX_MODULE_SET_<NAME>\fP, \fI\%CXX_MODULE_SET\fP and
\fI\%INTERFACE_CXX_MODULE_SETS\fP\&.
.SS CXX_MODULE_STD
.sp
Added in version 3.30.

.sp
\fBCXX_MODULE_STD\fP is a boolean specifying whether the target may use
\fBimport std;\fP its C++ sources or not.
.sp
\fBNOTE:\fP
.INDENT 0.0
.INDENT 3.5
This setting is meaningful only when experimental support for \fBimport
std;\fP has been enabled by the \fBCMAKE_EXPERIMENTAL_CXX_IMPORT_STD\fP gate.
.UNINDENT
.UNINDENT
.sp
When this property is explicitly set to \fBON\fP, CMake will add a dependency to
a target which provides the C++ standard library\(aqs modules for the C++
standard applied to the target. This target is only applicable within the
current build and will not appear in the exported interfaces of the targets.
When consumed, these targets will be reapplied as necessary.
.sp
\fBNOTE:\fP
.INDENT 0.0
.INDENT 3.5
Similar to the introduction of \fI\%CXX_SCAN_FOR_MODULES\fP, this
property defaults to \fBnot\fP adding \fBimport std\fP support to targets using
\fBcxx_std_23\fP without an explicit request in order to preserve existing
behavior for projects using C++23 without \fBimport std\fP\&. A future policy
to change the default behavior is expected once the feature sees wider
usage.
.UNINDENT
.UNINDENT
.sp
This property\(aqs value is not relevant for targets which disable scanning (see
\fI\%CXX_SCAN_FOR_MODULES\fP). Additionally, this property only applies to
targets utilizing C++23 (\fBcxx_std_23\fP) or newer.
.sp
The property supports
\fI\%generator expressions\fP, however
expressions that depend upon the configuration, the consuming target, or the
linker language are not allowed. Whether a target uses \fBimport std\fP should
not depend upon such things as it is a static property of the target\(aqs source
code.
.sp
Targets which are exported with C++ module sources will have this property\(aqs
resolved value exported.
.SS CXX_SCAN_FOR_MODULES
.sp
Added in version 3.28.

.sp
\fBCXX_SCAN_FOR_MODULES\fP is a boolean specifying whether CMake will scan C++
sources in the target for module dependencies.  See also the
\fI\%CXX_SCAN_FOR_MODULES\fP for per\-source settings which, if set,
overrides the target\-wide settings.
.sp
This property is initialized by the value of the
\fI\%CMAKE_CXX_SCAN_FOR_MODULES\fP variable if it is set when a target is
created.
.sp
When this property is set \fBON\fP or unset, CMake will scan the target\(aqs
\fBCXX\fP sources at build time and add module dependency information to the
compile line as necessary.  When this property is set \fBOFF\fP, CMake will not
scan the target\(aqs \fBCXX\fP sources at build time.
.sp
Note that scanning is only performed if C++20 or higher is enabled for the
target.  Scanning for modules in the target\(aqs sources belonging to file sets
of type \fBCXX_MODULES\fP is always performed.
.SS CXX_STANDARD
.sp
Added in version 3.1.

.sp
The C++ standard whose features are requested to build this target.
.sp
This property specifies the C++ standard whose features are requested
to build this target.  For some compilers, this results in adding a
flag such as \fB\-std=gnu++11\fP to the compile line.  For compilers that
have no notion of a standard level, such as Microsoft Visual C++ before
2015 Update 3, this has no effect.
.sp
Supported values are:
.INDENT 0.0
.TP
.B \fB98\fP
C++98
.TP
.B \fB11\fP
C++11
.TP
.B \fB14\fP
C++14
.TP
.B \fB17\fP
Added in version 3.8.

.sp
C++17
.TP
.B \fB20\fP
Added in version 3.12.

.sp
C++20
.TP
.B \fB23\fP
Added in version 3.20.

.sp
C++23
.TP
.B \fB26\fP
Added in version 3.25.

.sp
C++26. CMake 3.25 and later \fIrecognize\fP \fB26\fP as a valid value,
no version has support for any compiler.
.UNINDENT
.sp
If the value requested does not result in a compile flag being added for
the compiler in use, a previous standard flag will be added instead.  This
means that using:
.INDENT 0.0
.INDENT 3.5
.sp
.EX
set_property(TARGET tgt PROPERTY CXX_STANDARD 11)
.EE
.UNINDENT
.UNINDENT
.sp
with a compiler which does not support \fB\-std=gnu++11\fP or an equivalent
flag will not result in an error or warning, but will instead add the
\fB\-std=gnu++98\fP flag if supported.  This \(dqdecay\(dq behavior may be controlled
with the \fI\%CXX_STANDARD_REQUIRED\fP target property.
Additionally, the \fI\%CXX_EXTENSIONS\fP target property may be used to
control whether compiler\-specific extensions are enabled on a per\-target basis.
.sp
See the \fI\%cmake\-compile\-features(7)\fP manual for information on
compile features and a list of supported compilers.
.sp
This property is initialized by the value of
the \fI\%CMAKE_CXX_STANDARD\fP variable if it is set when a target
is created.
.SS CXX_STANDARD_REQUIRED
.sp
Added in version 3.1.

.sp
Boolean describing whether the value of \fI\%CXX_STANDARD\fP is a requirement.
.sp
If this property is set to \fBON\fP, then the value of the
\fI\%CXX_STANDARD\fP target property is treated as a requirement.  If this
property is \fBOFF\fP or unset, the \fI\%CXX_STANDARD\fP target property is
treated as optional and may \(dqdecay\(dq to a previous standard if the requested is
not available.  For compilers that have no notion of a standard level, such as
MSVC 1800 (Visual Studio 2013) and lower, this has no effect.
.sp
See the \fI\%cmake\-compile\-features(7)\fP manual for information on
compile features and a list of supported compilers.
.sp
This property is initialized by the value of
the \fI\%CMAKE_CXX_STANDARD_REQUIRED\fP variable if it is set when a
target is created.
.sp
Alternatively, see \fI\%Requiring Language Standards\fP\&.
.SS DEBUG_POSTFIX
.sp
See target property \fI\%<CONFIG>_POSTFIX\fP\&.
.sp
This property is a special case of the more\-general \fI\%<CONFIG>_POSTFIX\fP
property for the \fBDEBUG\fP configuration.
.SS DEBUGGER_WORKING_DIRECTORY
.sp
Added in version 4.0.

.sp
Sets the local debugger working directory for C++ targets.
The property value may use
\fI\%generator expressions\fP\&.
This property is initialized by the value of the variable
\fI\%CMAKE_DEBUGGER_WORKING_DIRECTORY\fP if it is set when a target is
created.
.sp
If the \fI\%VS_DEBUGGER_WORKING_DIRECTORY\fP property is also set, it will
take precedence over \fBDEBUGGER_WORKING_DIRECTORY\fP when using one of the
\fI\%Visual Studio Generators\fP\&.
.sp
Similarly, if \fI\%XCODE_SCHEME_WORKING_DIRECTORY\fP is set, it will
override \fBDEBUGGER_WORKING_DIRECTORY\fP when using the \fI\%Xcode\fP
generator.
.SS DEFINE_SYMBOL
.sp
Define a symbol when compiling this target\(aqs sources.
.sp
\fBDEFINE_SYMBOL\fP sets the name of the preprocessor symbol defined when
compiling sources in a shared library.  If not set here then it is set
to \fBtarget_EXPORTS\fP by default (with some substitutions if the target is
not a valid C identifier).  This is useful for headers to know whether
they are being included from inside their library or outside to
properly setup dllexport/dllimport decorations on Windows.
.sp
On POSIX platforms, this can optionally be used to control the visibility
of symbols.
.sp
CMake provides support for such decorations with the \fI\%GenerateExportHeader\fP
module.
.SS DEPLOYMENT_ADDITIONAL_FILES
.sp
Added in version 3.13.

.sp
Set the WinCE project \fBAdditionalFiles\fP in \fBDeploymentTool\fP in \fB\&.vcproj\fP
files generated by the \fI\%Visual Studio Generators\fP\&.
This is useful when you want to debug on remote WinCE device.
Specify additional files that will be copied to the device.
For example:
.INDENT 0.0
.INDENT 3.5
.sp
.EX
set_property(TARGET ${TARGET} PROPERTY
  DEPLOYMENT_ADDITIONAL_FILES \(dqenglish.lng|local_folder|remote_folder|0\(dq
  \(dqgerman.lng|local_folder|remote_folder|0\(dq)
.EE
.UNINDENT
.UNINDENT
.sp
produces:
.INDENT 0.0
.INDENT 3.5
.sp
.EX
<DeploymentTool AdditionalFiles=\(dqenglish.lng|local_folder|remote_folder|0;german.lng|local_folder|remote_folder|0\(dq ... />
.EE
.UNINDENT
.UNINDENT
.SS DEPLOYMENT_REMOTE_DIRECTORY
.sp
Added in version 3.6.

.sp
Set the WinCE project \fBRemoteDirectory\fP in \fBDeploymentTool\fP and
\fBRemoteExecutable\fP in \fBDebuggerTool\fP in \fB\&.vcproj\fP files generated
by the \fI\%Visual Studio Generators\fP\&.
This is useful when you want to debug on remote WinCE device.
For example:
.INDENT 0.0
.INDENT 3.5
.sp
.EX
set_property(TARGET ${TARGET} PROPERTY
  DEPLOYMENT_REMOTE_DIRECTORY \(dq\e\eFlashStorage\(dq)
.EE
.UNINDENT
.UNINDENT
.sp
produces:
.INDENT 0.0
.INDENT 3.5
.sp
.EX
<DeploymentTool RemoteDirectory=\(dq\eFlashStorage\(dq ... />
<DebuggerTool RemoteExecutable=\(dq\eFlashStorage\etarget_file\(dq ... />
.EE
.UNINDENT
.UNINDENT
.SS DEPRECATION
.sp
Added in version 3.17.

.sp
Deprecation message from imported target\(aqs developer.
.sp
\fBDEPRECATION\fP is the message regarding a deprecation status to be displayed
to downstream users of a target.
.sp
The message is formatted as follows:
.INDENT 0.0
.IP \(bu 2
Lines that do not start in whitespace are wrapped as paragraph text.
.IP \(bu 2
Lines that start in whitespace are preserved as preformatted text.
.UNINDENT
.SS DISABLE_PRECOMPILE_HEADERS
.sp
Added in version 3.16.

.sp
Disables the precompilation of header files specified by
\fI\%PRECOMPILE_HEADERS\fP property.
.sp
If the property is not set, CMake will use the value provided
by \fI\%CMAKE_DISABLE_PRECOMPILE_HEADERS\fP\&.
.SS DLL_NAME_WITH_SOVERSION
.sp
Added in version 3.27.

.sp
This property controls whether the \fI\%SOVERSION\fP target
property is added to the filename of generated DLL filenames
for the Windows platform, which is selected when the
\fI\%WIN32\fP variable is set.
.sp
The value of the listed property is appended to the
basename of the runtime component of the shared library
target as \fB\-<SOVERSION>\fP\&.
.sp
Please note that setting this property has no effect
if versioned filenames are globally disabled with the
\fI\%CMAKE_PLATFORM_NO_VERSIONED_SONAME\fP variable.
.SS DOTNET_SDK
.sp
Added in version 3.23.

.sp
Specify the .NET SDK for C# projects.  For example: \fBMicrosoft.NET.Sdk\fP\&.
.sp
This property tells \fI\%Visual Studio Generators\fP for VS 2019 and
above to generate a .NET SDK\-style project using the specified SDK.
The property is meaningful only to these generators, and only in C#
targets.  It is ignored for C++ projects, even if they are managed
(e.g. using \fI\%COMMON_LANGUAGE_RUNTIME\fP).
.sp
This property must be a non\-empty string to generate .NET SDK\-style projects.
CMake does not perform any validations for the value of the property.
.sp
This property may be initialized for all targets using the
\fI\%CMAKE_DOTNET_SDK\fP variable.
.sp
\fBNOTE:\fP
.INDENT 0.0
.INDENT 3.5
The \fI\%Visual Studio Generators\fP in this version of CMake have not
yet learned to support \fI\%add_custom_command()\fP in .NET SDK\-style
projects.  It is currently an error to attach a custom command to a
target with the \fBDOTNET_SDK\fP property set.
.UNINDENT
.UNINDENT
.SS DOTNET_TARGET_FRAMEWORK
.sp
Added in version 3.17.

.sp
Specify the .NET target framework.
.sp
Used to specify the .NET target framework for C++/CLI and C#.  For
example: \fBnetcoreapp2.1\fP\&.
.sp
This property is only evaluated for \fI\%Visual Studio Generators\fP
VS 2010 and above.
.sp
Can be initialized for all targets using the variable
\fI\%CMAKE_DOTNET_TARGET_FRAMEWORK\fP\&.
.SS DOTNET_TARGET_FRAMEWORK_VERSION
.sp
Added in version 3.12.

.sp
Specify the .NET target framework version.
.sp
Used to specify the .NET target framework version for C++/CLI and C#.
For example: \fBv4.5\fP\&.
.sp
This property is only evaluated for \fI\%Visual Studio Generators\fP
VS 2010 and above.
.sp
To initialize this variable for all targets set
\fI\%CMAKE_DOTNET_TARGET_FRAMEWORK\fP or
\fI\%CMAKE_DOTNET_TARGET_FRAMEWORK_VERSION\fP\&. If both are set,
the latter is ignored.
.SS EchoString
.sp
A message to be displayed when the target is built.
.sp
A message to display on some generators (such as \fI\%Makefile Generators\fP)
when the target is built.
.SS ENABLE_EXPORTS
.sp
Specify whether an executable or a shared library exports symbols.
.sp
Normally an executable does not export any symbols because it is the
final program.  It is possible for an executable to export symbols to
be used by loadable modules.  When this property is set to true CMake
will allow other targets to \(dqlink\(dq to the executable with the
\fI\%target_link_libraries()\fP command.  On all platforms a target\-level
dependency on the executable is created for targets that link to it.
Handling of the executable on the link lines of the loadable modules
varies by platform:
.INDENT 0.0
.IP \(bu 2
On Windows\-based systems (including Cygwin) an \(dqimport library\(dq is
created along with the executable to list the exported symbols.
Loadable modules link to the import library to get the symbols.
.IP \(bu 2
On macOS, loadable modules link to the executable itself using the
\fB\-bundle_loader\fP flag.
.IP \(bu 2
On AIX, a linker \(dqimport file\(dq is created along with the executable
to list the exported symbols for import when linking other targets.
Loadable modules link to the import file to get the symbols.
.IP \(bu 2
On other platforms, loadable modules are simply linked without
referencing the executable since the dynamic loader will
automatically bind symbols when the module is loaded.
.UNINDENT
.sp
This property is initialized by the value of the
\fI\%CMAKE_EXECUTABLE_ENABLE_EXPORTS\fP variable, if it is set when an
executable target is created.  If \fI\%CMAKE_EXECUTABLE_ENABLE_EXPORTS\fP
is not set, the \fI\%CMAKE_ENABLE_EXPORTS\fP variable is used to initialize
the property instead for backward compatibility reasons.
See below for alternative initialization behavior for shared library targets.
.sp
Added in version 3.27: To link with a shared library on macOS, or to a shared framework on any Apple
platform, a linker import file can be used instead of the actual shared
library. These linker import files are also known as text\-based stubs, and
they have a \fB\&.tbd\fP file extension.
.sp
The generation of these linker import files, as well as their consumption, is
controlled by this property. When this property is set to true on a shared
library target, CMake will generate a \fB\&.tbd\fP file for the library.
Other targets that link to the shared library target will then use this
\fB\&.tbd\fP file when linking rather than linking to the shared library binary.
.sp
\fBNOTE:\fP
.INDENT 0.0
.INDENT 3.5
For backward compatibility reasons, this property will be ignored if the
\fI\%XCODE_ATTRIBUTE_GENERATE_TEXT_BASED_STUBS\fP
target property or the
\fI\%CMAKE_XCODE_ATTRIBUTE_GENERATE_TEXT_BASED_STUBS\fP
variable is set to false.
.UNINDENT
.UNINDENT
.sp
For shared library targets, this property is initialized by the value of the
\fI\%CMAKE_SHARED_LIBRARY_ENABLE_EXPORTS\fP variable, if it is set when
the target is created.

.SS EXCLUDE_FROM_ALL
.sp
Set this target property to a true (or false) value to exclude (or include)
the target from the \(dqall\(dq target of the containing directory and its
ancestors.  If excluded, running e.g. \fBmake\fP in the containing directory
or its ancestors will not build the target by default.
.sp
If this target property is not set then the target will be included in
the \(dqall\(dq target of the containing directory.  Furthermore, it will be
included in the \(dqall\(dq target of its ancestor directories unless the
\fI\%EXCLUDE_FROM_ALL\fP directory property is set.
.sp
With \fBEXCLUDE_FROM_ALL\fP set to false or not set at all, the target
will be brought up to date as part of doing a \fBmake install\fP or its
equivalent for the CMake generator being used.
.sp
If a target has \fBEXCLUDE_FROM_ALL\fP set to true, it may still be listed
in an \fI\%install(TARGETS)\fP command, but the user is responsible for
ensuring that the target\(aqs build artifacts are not missing or outdated when
an install is performed.
.sp
This property may use \(dqgenerator expressions\(dq with the syntax \fB$<...>\fP\&. See
the \fI\%cmake\-generator\-expressions(7)\fP manual for available expressions.
.sp
Only the \(dqNinja Multi\-Config\(dq generator supports a property value that varies by
configuration.  For all other generators the value of this property must be the
same for all configurations.
.SS See Also
.INDENT 0.0
.IP \(bu 2
To exclude targets from the whole directory subtree, see the
\fI\%EXCLUDE_FROM_ALL\fP directory property.
.IP \(bu 2
To exclude targets from the Visual Studio solution build, use
\fI\%EXCLUDE_FROM_DEFAULT_BUILD\fP\&.
.UNINDENT
.SS EXCLUDE_FROM_DEFAULT_BUILD
.sp
Exclude a target from the solution build configuration.
.sp
This property is only used by \fI\%Visual Studio Generators\fP\&. When set to
\fBTRUE\fP, the target will be excluded from the build when the \(dqBuild Solution\(dq
command is run.
.sp
This property has a per\-configuration version:
\fI\%EXCLUDE_FROM_DEFAULT_BUILD_<CONFIG>\fP\&.
.sp
\fBNOTE:\fP
.INDENT 0.0
.INDENT 3.5
Solution build configurations do not take project dependencies into account.
If a target is excluded, it will not be built, even if another target
included in the configuration depends on it. This behavior differs from the
CMake\-generated \fBALL_BUILD\fP target and the \fI\%EXCLUDE_FROM_ALL\fP
property.
.UNINDENT
.UNINDENT
.SS EXCLUDE_FROM_DEFAULT_BUILD_<CONFIG>
.sp
Per\-configuration version of target exclusion from \fBBuild Solution\fP\&.
.sp
This is the configuration\-specific version of
\fI\%EXCLUDE_FROM_DEFAULT_BUILD\fP\&.  If the generic
\fI\%EXCLUDE_FROM_DEFAULT_BUILD\fP is also set on a target,
\fBEXCLUDE_FROM_DEFAULT_BUILD_<CONFIG>\fP takes
precedence in configurations for which it has a value.
.SS EXPORT_BUILD_DATABASE
.sp
Added in version 3.31.

.sp
Enable/Disable output of a build database for a target.
.sp
This property is initialized by the value of the variable
\fI\%CMAKE_EXPORT_BUILD_DATABASE\fP if it is set when a target is created.
.sp
\fBNOTE:\fP
.INDENT 0.0
.INDENT 3.5
This property is meaningful only when experimental support for build
databases has been enabled by the
\fBCMAKE_EXPERIMENTAL_EXPORT_BUILD_DATABASE\fP gate.
.UNINDENT
.UNINDENT
.SS EXPORT_COMPILE_COMMANDS
.sp
Added in version 3.20.

.sp
Enable/Disable output of compile commands during generation for a target.
.sp
This property is initialized by the value of the variable
\fI\%CMAKE_EXPORT_COMPILE_COMMANDS\fP if it is set when a target is created.
.SS EXPORT_FIND_PACKAGE_NAME
.sp
\fBNOTE:\fP
.INDENT 0.0
.INDENT 3.5
Experimental. Gated by \fBCMAKE_EXPERIMENTAL_EXPORT_PACKAGE_DEPENDENCIES\fP\&.
.UNINDENT
.UNINDENT
.sp
Control the package name associated with a dependency target when exporting a
\fI\%find_dependency()\fP call in \fI\%install(EXPORT)\fP or
\fI\%export(EXPORT)\fP\&. This can be used to assign a package name to a
package that is built by CMake and exported, or to override the package in the
\fI\%find_package()\fP call that created the target.
.sp
This property is initialized by \fI\%CMAKE_EXPORT_FIND_PACKAGE_NAME\fP\&.
.SS EXPORT_NAME
.sp
Exported name for target files.
.sp
This sets the name for the \fBIMPORTED\fP target generated by the
\fI\%install(EXPORT)\fP and \fI\%export()\fP commands.
If not set, the logical target name is used by default.
.SS EXPORT_NO_SYSTEM
.sp
Added in version 3.25.

.sp
This property affects the behavior of the \fI\%install(EXPORT)\fP and
\fI\%export()\fP commands when they install or export the target respectively.
When \fBEXPORT_NO_SYSTEM\fP is set to true, those commands generate an imported
target with \fI\%SYSTEM\fP property set to false.
.sp
See the \fI\%NO_SYSTEM_FROM_IMPORTED\fP target property to set this
behavior on the target \fIconsuming\fP the include directories rather than the
one \fIproviding\fP them.
.SS EXPORT_PROPERTIES
.sp
Added in version 3.12.

.sp
List additional properties to export for a target.
.sp
This property contains a list of property names that should be exported by
the \fI\%install(EXPORT)\fP and \fI\%export()\fP commands.  By default
only a limited number of properties are exported. This property can be used
to additionally export other properties as well.
.sp
Properties starting with \fBINTERFACE_\fP or \fBIMPORTED_\fP are not allowed as
they are reserved for internal CMake use.
.sp
Properties containing generator expressions are also not allowed.
.sp
\fBNOTE:\fP
.INDENT 0.0
.INDENT 3.5
Since CMake 3.19, \fI\%Interface Libraries\fP may have arbitrary
target properties.  If a project exports an interface library
with custom properties, the resulting package may not work with
dependents configured by older versions of CMake that reject the
custom properties.
.UNINDENT
.UNINDENT
.SS FOLDER
.sp
For IDEs that present targets using a folder hierarchy, this property
specifies the name of the folder to place the target under.
To nest folders, use \fBFOLDER\fP values such as \fBGUI/Dialogs\fP with \fB/\fP
characters separating folder levels.  Targets with no \fBFOLDER\fP property
will appear as top level entities.  Targets with the same \fBFOLDER\fP
property value will appear in the same folder as siblings.
.sp
Only some CMake generators honor the \fBFOLDER\fP property
(e.g. \fI\%Xcode\fP or any of the
\fI\%Visual Studio\fP generators).
Those generators that don\(aqt will simply ignore it.
.sp
This property is initialized by the value of the variable
\fI\%CMAKE_FOLDER\fP if it is set when a target is created.
.sp
The global property \fI\%USE_FOLDERS\fP must be set to true, otherwise
the \fBFOLDER\fP property is ignored.
.SS Fortran_BUILDING_INTRINSIC_MODULES
.sp
Added in version 4.0.

.sp
Instructs the CMake Fortran preprocessor that the target is building
Fortran intrinsics for building a Fortran compiler.
.sp
This property is off by default and should be turned only on projects
that build a Fortran compiler. It should not be turned on for projects
that use a Fortran compiler.
.sp
Turning this property on will correctly add dependencies for building
Fortran intrinsic modules whereas turning the property off will ignore
Fortran intrinsic modules in the dependency graph as they are supplied
by the compiler itself.
.SS Fortran_FORMAT
.sp
Set to \fBFIXED\fP or \fBFREE\fP to indicate the Fortran source layout.
.sp
This property tells CMake whether the Fortran source files in a target
use fixed\-format or free\-format.  CMake will pass the corresponding
format flag to the compiler.  Use the source\-specific \fBFortran_FORMAT\fP
property to change the format of a specific source file.  If the
variable \fI\%CMAKE_Fortran_FORMAT\fP is set when a target is created its
value is used to initialize this property.
.SS Fortran_MODULE_DIRECTORY
.sp
Specify output directory for Fortran modules provided by the target.
.sp
If the target contains Fortran source files that provide modules and
the compiler supports a module output directory this specifies the
directory in which the modules will be placed.  When this property is
not set the modules will be placed in the build directory
corresponding to the target\(aqs source directory.  If the variable
\fI\%CMAKE_Fortran_MODULE_DIRECTORY\fP is set when a target is created its
value is used to initialize this property.
.sp
When using one of the \fI\%Visual Studio Generators\fP with the Intel Fortran
plugin installed in Visual Studio, a subdirectory named after the
configuration will be appended to the path where modules are created.
For example, if \fBFortran_MODULE_DIRECTORY\fP is set to \fBC:/some/path\fP,
modules will end up in \fBC:/some/path/Debug\fP (or
\fBC:/some/path/Release\fP etc.) when an Intel Fortran \fB\&.vfproj\fP file is
generated, and in \fBC:/some/path\fP when any other generator is used.
.sp
Note that some compilers will automatically search the module output
directory for modules USEd during compilation but others will not.  If
your sources USE modules their location must be specified by
\fI\%INCLUDE_DIRECTORIES\fP regardless of this property.
.SS Fortran_PREPROCESS
.sp
Added in version 3.18.

.sp
Control whether the Fortran source file should be unconditionally
preprocessed.
.sp
If unset or empty, rely on the compiler to determine whether the file
should be preprocessed. If explicitly set to \fBOFF\fP then the file does not
need to be preprocessed. If explicitly set to \fBON\fP, then the file does
need to be preprocessed as part of the compilation step.
.sp
When using the \fI\%Ninja\fP generator, all source files are
first preprocessed in order to generate module dependency
information. Setting this property to \fBOFF\fP will make \fBNinja\fP
skip this step.
.sp
Use the source\-specific \fI\%Fortran_PREPROCESS\fP property if a single
file needs to be preprocessed. If the variable
\fI\%CMAKE_Fortran_PREPROCESS\fP is set when a target is created its
value is used to initialize this property.
.sp
\fBNOTE:\fP
.INDENT 0.0
.INDENT 3.5
For some compilers, \fBNAG\fP, \fBPGI\fP and \fBSolaris Studio\fP,
setting this to \fBOFF\fP will have no effect.
.UNINDENT
.UNINDENT
.SS FRAMEWORK
.sp
Build \fBSHARED\fP or \fBSTATIC\fP library as Framework Bundle on the macOS and iOS.
.sp
If such a library target has this property set to \fBTRUE\fP it will be
built as a framework when built on the macOS and iOS.  It will have the
directory structure required for a framework and will be suitable to
be used with the \fB\-framework\fP option.  This property is initialized by the
value of the \fI\%CMAKE_FRAMEWORK\fP variable if it is set when a target is
created.
.sp
To customize \fBInfo.plist\fP file in the framework, use
\fI\%MACOSX_FRAMEWORK_INFO_PLIST\fP target property.
.sp
For macOS see also the \fI\%FRAMEWORK_VERSION\fP target property.
.sp
Example of creation \fBdynamicFramework\fP:
.INDENT 0.0
.INDENT 3.5
.sp
.EX
add_library(dynamicFramework SHARED
            dynamicFramework.c
            dynamicFramework.h
)
set_target_properties(dynamicFramework PROPERTIES
  FRAMEWORK TRUE
  FRAMEWORK_VERSION C
  MACOSX_FRAMEWORK_IDENTIFIER com.cmake.dynamicFramework
  MACOSX_FRAMEWORK_INFO_PLIST Info.plist
  # \(dqcurrent version\(dq in semantic format in Mach\-O binary file
  VERSION 16.4.0
  # \(dqcompatibility version\(dq in semantic format in Mach\-O binary file
  SOVERSION 1.0.0
  PUBLIC_HEADER dynamicFramework.h
  XCODE_ATTRIBUTE_CODE_SIGN_IDENTITY \(dqiPhone Developer\(dq
)
.EE
.UNINDENT
.UNINDENT
.SS FRAMEWORK_MULTI_CONFIG_POSTFIX_<CONFIG>
.sp
Added in version 3.18.

.sp
Postfix to append to the framework file name for configuration \fB<CONFIG>\fP,
when using a multi\-config generator (like \fI\%Xcode\fP and
\fI\%Ninja Multi\-Config\fP).
.sp
When building with configuration \fB<CONFIG>\fP the value of this property
is appended to the framework file name built on disk.
.sp
For example, given a framework called \fBmy_fw\fP, a value of \fB_debug\fP
for the \fBFRAMEWORK_MULTI_CONFIG_POSTFIX_DEBUG\fP property, and
\fBDebug;Release\fP in \fI\%CMAKE_CONFIGURATION_TYPES\fP, the following
relevant files would be created for the \fBDebug\fP and \fBRelease\fP
configurations:
.INDENT 0.0
.IP \(bu 2
\fBRelease/my_fw.framework/my_fw\fP
.IP \(bu 2
\fBRelease/my_fw.framework/Versions/A/my_fw\fP
.IP \(bu 2
\fBDebug/my_fw.framework/my_fw_debug\fP
.IP \(bu 2
\fBDebug/my_fw.framework/Versions/A/my_fw_debug\fP
.UNINDENT
.sp
For framework targets, this property is initialized by the value of the
\fI\%CMAKE_FRAMEWORK_MULTI_CONFIG_POSTFIX_<CONFIG>\fP variable if it
is set when a target is created.
.sp
This property is ignored for non\-framework targets, and when using single
config generators.
.SS FRAMEWORK_VERSION
.sp
Added in version 3.4.

.sp
Version of a framework created using the \fI\%FRAMEWORK\fP target
property (e.g. \fBA\fP).
.sp
This property only affects macOS, as iOS doesn\(aqt have versioned
directory structure.
.SS GENERATOR_FILE_NAME
.sp
Generator\(aqs file for this target.
.sp
An internal property used by some generators to record the name of the
project or dsp file associated with this target.  Note that at
configure time, this property is only set for targets created by
\fI\%include_external_msproject()\fP\&.
.SS GHS_INTEGRITY_APP
.sp
Added in version 3.14.

.sp
\fBON\fP / \fBOFF\fP boolean to determine if an executable target should
be treated as an \fBIntegrity Application\fP\&.
.sp
If no value is set and if a \fB\&.int\fP file is added as a source file to the
executable target it will be treated as an \fBIntegrity Application\fP\&.
.sp
Supported on \fI\%Green Hills MULTI\fP\&.
.SS GHS_NO_SOURCE_GROUP_FILE
.sp
Added in version 3.14.

.sp
\fBON\fP / \fBOFF\fP boolean to control if the project file for a target should
be one single file or multiple files.
.sp
The default behavior or when the property is \fBOFF\fP is to generate a project
file for the target and then a sub\-project file for each source group.
.sp
When this property is \fBON\fP or if \fI\%CMAKE_GHS_NO_SOURCE_GROUP_FILE\fP
is \fBON\fP then only a single project file is generated for the target.
.sp
Supported on \fI\%Green Hills MULTI\fP\&.
.SS GNUtoMS
.sp
Convert GNU import library (\fB\&.dll.a\fP) to MS format (\fB\&.lib\fP).
.sp
When linking a shared library or executable that exports symbols using
GNU tools on Windows (MinGW/MSYS) with Visual Studio installed convert
the import library (\fB\&.dll.a\fP) from GNU to MS format (\fB\&.lib\fP).  Both import
libraries will be installed by \fI\%install(TARGETS)\fP and exported by
\fI\%install(EXPORT)\fP and  \fI\%export()\fP to be linked
by applications with either GNU\- or MS\-compatible tools.
.sp
If the variable \fBCMAKE_GNUtoMS\fP is set when a target is created its
value is used to initialize this property.  The variable must be set
prior to the first command that enables a language such as \fI\%project()\fP
or \fI\%enable_language()\fP\&.  CMake provides the variable as an option to the
user automatically when configuring on Windows with GNU tools.
.SS HAS_CXX
.sp
Link the target using the C++ linker tool (obsolete).
.sp
This is equivalent to setting the \fI\%LINKER_LANGUAGE\fP
property to \fBCXX\fP\&.
.SS HEADER_DIRS
.sp
Added in version 3.23.

.sp
Semicolon\-separated list of base directories of the target\(aqs default
header set (i.e. the file set with name and type \fBHEADERS\fP). The property
supports \fI\%generator expressions\fP\&.
.sp
This property is normally only set by \fI\%target_sources(FILE_SET)\fP
rather than being manipulated directly.
.sp
See \fI\%HEADER_DIRS_<NAME>\fP for the list of base directories in
other header sets.
.SS HEADER_DIRS_<NAME>
.sp
Added in version 3.23.

.sp
Semicolon\-separated list of base directories of the target\(aqs \fB<NAME>\fP
header set, which has the set type \fBHEADERS\fP\&. The property supports
\fI\%generator expressions\fP\&.
.sp
This property is normally only set by \fI\%target_sources(FILE_SET)\fP
rather than being manipulated directly.
.sp
See \fI\%HEADER_DIRS\fP for the list of base directories in the
default header set. See \fI\%HEADER_SETS\fP for the file set names of all
header sets.
.SS HEADER_SET
.sp
Added in version 3.23.

.sp
Semicolon\-separated list of files in the target\(aqs default header set,
(i.e. the file set with name and type \fBHEADERS\fP). If any of the paths
are relative, they are computed relative to the target\(aqs source directory.
The property supports
\fI\%generator expressions\fP\&.
.sp
This property is normally only set by \fI\%target_sources(FILE_SET)\fP
rather than being manipulated directly.
.sp
See \fI\%HEADER_SET_<NAME>\fP for the list of files in other header sets.
.SS HEADER_SET_<NAME>
.sp
Added in version 3.23.

.sp
Semicolon\-separated list of files in the target\(aqs \fB<NAME>\fP header set,
which has the set type \fBHEADERS\fP\&. If any of the paths are relative,
they are computed relative to the target\(aqs source directory. The property
supports \fI\%generator expressions\fP\&.
.sp
This property is normally only set by \fI\%target_sources(FILE_SET)\fP
rather than being manipulated directly.
.sp
See \fI\%HEADER_SET\fP for the list of files in the default header set.
See \fI\%HEADER_SETS\fP for the file set names of all header sets.
.SS HEADER_SETS
.sp
Added in version 3.23.

.sp
Read\-only list of the target\(aqs \fBPRIVATE\fP and \fBPUBLIC\fP header sets (i.e.
all file sets with the type \fBHEADERS\fP). Files listed in these file sets are
treated as source files for the purpose of IDE integration. The files also
have their \fI\%HEADER_FILE_ONLY\fP property set to \fBTRUE\fP\&.
.sp
Header sets may be defined using the \fI\%target_sources()\fP command
\fBFILE_SET\fP option with type \fBHEADERS\fP\&.
.sp
See also \fI\%HEADER_SET_<NAME>\fP, \fI\%HEADER_SET\fP and
\fI\%INTERFACE_HEADER_SETS\fP\&.
.SS HIP_ARCHITECTURES
.sp
Added in version 3.21.

.sp
List of GPU architectures to for which to generate device code.
Architecture names are interpreted based on \fI\%CMAKE_HIP_PLATFORM\fP\&.
.sp
A non\-empty false value (e.g. \fBOFF\fP) disables adding architectures.
This is intended to support packagers and rare cases where full control
over the passed flags is required.
.sp
This property is initialized by the value of the \fI\%CMAKE_HIP_ARCHITECTURES\fP
variable if it is set when a target is created.
.sp
The HIP compilation model has two modes: whole and separable. Whole compilation
generates device code at compile time. Separable compilation generates device
code at link time. Therefore the \fBHIP_ARCHITECTURES\fP target property should
be set on targets that compile or link with any HIP sources.
.SS Examples
.INDENT 0.0
.INDENT 3.5
.sp
.EX
set_property(TARGET tgt PROPERTY HIP_ARCHITECTURES gfx801 gfx900)
.EE
.UNINDENT
.UNINDENT
.sp
Generates code for both \fBgfx801\fP and \fBgfx900\fP\&.
.SS HIP_EXTENSIONS
.sp
Added in version 3.21.

.sp
Boolean specifying whether compiler specific extensions are requested.
.sp
This property specifies whether compiler specific extensions should be
used.  For some compilers, this results in adding a flag such
as \fB\-std=gnu++11\fP instead of \fB\-std=c++11\fP to the compile line.  This
property is \fBON\fP by default. The basic HIP/C++ standard level is
controlled by the \fI\%HIP_STANDARD\fP target property.
.sp
See the \fI\%cmake\-compile\-features(7)\fP manual for information on
compile features and a list of supported compilers.
.sp
This property is initialized by the value of
the \fI\%CMAKE_HIP_EXTENSIONS\fP variable if set when a target is created
and otherwise by the value of
\fI\%CMAKE_HIP_EXTENSIONS_DEFAULT\fP (see
\fI\%CMP0128\fP).
.SS HIP_STANDARD
.sp
Added in version 3.21.

.sp
The HIP/C++ standard requested to build this target.
.sp
Supported values are:
.INDENT 0.0
.TP
.B \fB98\fP
HIP C++98
.TP
.B \fB11\fP
HIP C++11
.TP
.B \fB14\fP
HIP C++14
.TP
.B \fB17\fP
HIP C++17
.TP
.B \fB20\fP
HIP C++20
.TP
.B \fB23\fP
HIP C++23
.TP
.B \fB26\fP
Added in version 3.25.

.sp
HIP C++26. CMake 3.25 and later \fIrecognize\fP \fB26\fP as a valid value,
no version has support for any compiler.
.UNINDENT
.sp
If the value requested does not result in a compile flag being added for
the compiler in use, a previous standard flag will be added instead.  This
means that using:
.INDENT 0.0
.INDENT 3.5
.sp
.EX
set_property(TARGET tgt PROPERTY HIP_STANDARD 11)
.EE
.UNINDENT
.UNINDENT
.sp
with a compiler which does not support \fB\-std=gnu++11\fP or an equivalent
flag will not result in an error or warning, but will instead add the
\fB\-std=gnu++98\fP flag if supported.  This \(dqdecay\(dq behavior may be controlled
with the \fI\%HIP_STANDARD_REQUIRED\fP target property.
Additionally, the \fI\%HIP_EXTENSIONS\fP target property may be used to
control whether compiler\-specific extensions are enabled on a per\-target basis.
.sp
See the \fI\%cmake\-compile\-features(7)\fP manual for information on
compile features and a list of supported compilers.
.sp
This property is initialized by the value of
the \fI\%CMAKE_HIP_STANDARD\fP variable if it is set when a target
is created.
.SS HIP_STANDARD_REQUIRED
.sp
Added in version 3.21.

.sp
Boolean describing whether the value of \fI\%HIP_STANDARD\fP is a requirement.
.sp
If this property is set to \fBON\fP, then the value of the
\fI\%HIP_STANDARD\fP target property is treated as a requirement.  If this
property is \fBOFF\fP or unset, the \fI\%HIP_STANDARD\fP target property is
treated as optional and may \(dqdecay\(dq to a previous standard if the requested is
not available.
.sp
See the \fI\%cmake\-compile\-features(7)\fP manual for information on
compile features and a list of supported compilers.
.sp
This property is initialized by the value of
the \fI\%CMAKE_HIP_STANDARD_REQUIRED\fP variable if it is set when a
target is created.
.SS IMPLICIT_DEPENDS_INCLUDE_TRANSFORM
.sp
Specify \fB#include\fP line transforms for dependencies in a target.
.sp
This property specifies rules to transform macro\-like \fB#include\fP lines
during implicit dependency scanning of C and C++ source files.  The
list of rules must be semicolon\-separated with each entry of the form
\fBA_MACRO(%)=value\-with\-%\fP (the \fB%\fP must be literal).  During dependency
scanning occurrences of \fBA_MACRO(...)\fP on \fB#include\fP lines will be
replaced by the value given with the macro argument substituted for
\fB%\fP\&.  For example, the entry
.INDENT 0.0
.INDENT 3.5
.sp
.EX
MYDIR(%)=<mydir/%>
.EE
.UNINDENT
.UNINDENT
.sp
will convert lines of the form
.INDENT 0.0
.INDENT 3.5
.sp
.EX
#include MYDIR(myheader.h)
.EE
.UNINDENT
.UNINDENT
.sp
to
.INDENT 0.0
.INDENT 3.5
.sp
.EX
#include <mydir/myheader.h>
.EE
.UNINDENT
.UNINDENT
.sp
allowing the dependency to be followed.
.sp
This property applies to sources in the target on which it is set.
.SS IMPORTED
.sp
Read\-only indication of whether a target is \fBIMPORTED\fP\&.
.sp
The boolean value of this property is \fBTrue\fP for targets created with
the \fBIMPORTED\fP option to \fI\%add_executable()\fP or \fI\%add_library()\fP\&.
It is \fBFalse\fP for targets built within the project.
.SS IMPORTED_COMMON_LANGUAGE_RUNTIME
.sp
Added in version 3.12.

.sp
Property to define if the target uses \fBC++/CLI\fP\&.
.sp
Ignored for non\-imported targets.
.sp
See also the \fI\%COMMON_LANGUAGE_RUNTIME\fP target property.
.SS IMPORTED_CONFIGURATIONS
.sp
Configurations provided for an \fI\%imported target\fP\&.
.sp
Set this to the list of configuration names available for an imported
target.  For each configuration named, the imported target\(aqs artifacts
must be specified in other target properties:
.INDENT 0.0
.IP \(bu 2
\fI\%IMPORTED_LOCATION_<CONFIG>\fP, or
.IP \(bu 2
\fI\%IMPORTED_IMPLIB_<CONFIG>\fP (on DLL platforms, on AIX for
\fI\%Executables\fP or on Apple for \fI\%Shared Libraries\fP), or
.IP \(bu 2
\fI\%IMPORTED_OBJECTS_<CONFIG>\fP (for \fI\%Object Libraries\fP), or
.IP \(bu 2
\fI\%IMPORTED_LIBNAME_<CONFIG>\fP (for \fI\%Interface Libraries\fP).
.UNINDENT
.sp
The configuration names correspond to those defined in the project from
which the target is imported.  If the importing project uses a different
set of configurations, the names may be mapped using the
\fI\%MAP_IMPORTED_CONFIG_<CONFIG>\fP target property.
.sp
The \fBIMPORTED_CONFIGURATIONS\fP property is ignored for non\-imported targets.
.SS IMPORTED_CXX_MODULES_COMPILE_DEFINITIONS
.sp
Added in version 3.28.

.sp
Preprocessor definitions for compiling an \fBIMPORTED\fP target\(aqs C++ module
sources.
.sp
CMake will automatically drop some definitions that are not supported
by the native build tool.
.SS IMPORTED_CXX_MODULES_COMPILE_FEATURES
.sp
Added in version 3.28.

.sp
Compiler features enabled for this \fBIMPORTED\fP target\(aqs C++ modules.
.sp
The value of this property is used by the generators to set the include
paths for the compiler.
.SS IMPORTED_CXX_MODULES_COMPILE_OPTIONS
.sp
Added in version 3.28.

.sp
List of options to pass to the compiler for this \fBIMPORTED\fP target\(aqs C++
modules.
.SS Option De\-duplication
.sp
The final set of options used for a target is constructed by
accumulating options from the current target and the usage requirements of
its dependencies.  The set of options is de\-duplicated to avoid repetition.
.sp
Added in version 3.12: While beneficial for individual options, the de\-duplication step can break
up option groups.  For example, \fB\-option A \-option B\fP becomes
\fB\-option A B\fP\&.  One may specify a group of options using shell\-like
quoting along with a \fBSHELL:\fP prefix.  The \fBSHELL:\fP prefix is dropped,
and the rest of the option string is parsed using the
\fI\%separate_arguments()\fP \fBUNIX_COMMAND\fP mode. For example,
\fB\(dqSHELL:\-option A\(dq \(dqSHELL:\-option B\(dq\fP becomes \fB\-option A \-option B\fP\&.

.SS IMPORTED_CXX_MODULES_INCLUDE_DIRECTORIES
.sp
Added in version 3.28.

.sp
List of preprocessor include file search directories when compiling C++
modules for \fBIMPORTED\fP targets.
.sp
The value of this property is used by the generators to set the include
paths for the compiler.
.SS IMPORTED_CXX_MODULES_LINK_LIBRARIES
.sp
Added in version 3.28.

.sp
List of direct dependencies to use for usage requirements for C++ modules in
the target\(aqs C++ modules.
.SS IMPORTED_GLOBAL
.sp
Added in version 3.11.

.sp
Indication of whether an \fI\%IMPORTED target\fP is
globally visible.
.sp
The boolean value of this property is True for targets created with the
\fBIMPORTED\fP \fBGLOBAL\fP options to \fI\%add_executable()\fP or
\fI\%add_library()\fP\&. It is always False for targets built within the
project.
.sp
For targets created with the \fBIMPORTED\fP option to
\fI\%add_executable()\fP or \fI\%add_library()\fP but without the
additional option \fBGLOBAL\fP this is False, too. However, setting this
property for such a locally \fBIMPORTED\fP target to True promotes that
target to global scope. This promotion can only be done in the same
directory where that \fBIMPORTED\fP target was created in the first place.
.sp
\fBNOTE:\fP
.INDENT 0.0
.INDENT 3.5
Once an imported target has been made global, it cannot be changed back to
non\-global. Therefore, if a project sets this property, it may only
provide a value of True. CMake will issue an error if the project tries to
set the property to a non\-True value, even if the value was already False.
.UNINDENT
.UNINDENT
.sp
\fBNOTE:\fP
.INDENT 0.0
.INDENT 3.5
Local \fI\%ALIAS targets\fP created before promoting an
\fI\%IMPORTED target\fP from \fBLOCAL\fP to \fBGLOBAL\fP, keep
their initial scope (see \fI\%ALIAS_GLOBAL\fP target property).
.UNINDENT
.UNINDENT
.SS IMPORTED_IMPLIB
.sp
Full path to the import library for an \fBIMPORTED\fP target.
.sp
This property may be set:
.INDENT 0.0
.IP \(bu 2
On DLL platforms, to the location of the \fB\&.lib\fP part of the DLL.
.IP \(bu 2
Added in version 3.16: On AIX, to an import file (e.g. \fB\&.imp\fP) created for executables that
export symbols (see the \fI\%ENABLE_EXPORTS\fP target property).

.IP \(bu 2
Added in version 3.27: On Apple platforms, to an import file (e.g. \fB\&.tbd\fP) created for shared
libraries or frameworks (see the \fI\%ENABLE_EXPORTS\fP target
property).  For frameworks, this is the location of the \fB\&.tbd\fP file
symlink just inside the framework folder.

.IP \(bu 2
Added in version 3.28: On non\-DLL platforms, to the location of a shared library.
When set without also specifying an \fI\%IMPORTED_LOCATION\fP,
the library is considered to be a stub, and its location will not
be added as a runtime search path to dependents that link it.

.UNINDENT
.sp
Changed in version 3.28: If an imported target is an Apple framework or XCFramework, the preferred
arrangement is to set \fI\%IMPORTED_LOCATION\fP to the \fB\&.framework\fP
or \fB\&.xcframework\fP directory.  CMake will then find the relevant \fB\&.tbd\fP
file inside that framework or XCFramework automatically without requiring
\fBIMPORTED_IMPLIB\fP to be set.

.sp
The \fBIMPORTED_IMPLIB\fP target property may be overridden for a
given configuration \fB<CONFIG>\fP by the configuration\-specific
\fI\%IMPORTED_IMPLIB_<CONFIG>\fP target property.  Furthermore,
the \fI\%MAP_IMPORTED_CONFIG_<CONFIG>\fP target property may be
used to map between a project\(aqs configurations and those of an imported
target.  If none of these is set then the name of any other configuration
listed in the \fI\%IMPORTED_CONFIGURATIONS\fP target property may be
selected and its \fI\%IMPORTED_IMPLIB_<CONFIG>\fP value used.
.sp
This property is ignored for non\-imported targets.
.SS IMPORTED_IMPLIB_<CONFIG>
.sp
<CONFIG>\-specific version of \fI\%IMPORTED_IMPLIB\fP property.
.sp
Configuration names correspond to those provided by the project from
which the target is imported.
.SS IMPORTED_LIBNAME
.sp
Added in version 3.8.

.sp
Specify the link library name for an \fI\%imported\fP
\fI\%Interface Library\fP\&.
.sp
An interface library builds no library file itself but does specify
usage requirements for its consumers.  The \fBIMPORTED_LIBNAME\fP
property may be set to specify a single library name to be placed
on the link line in place of the interface library target name as
a requirement for using the interface.
.sp
This property is intended for use in naming libraries provided by
a platform SDK for which the full path to a library file may not
be known.  The value may be a plain library name such as \fBfoo\fP
but may \fInot\fP be a path (e.g. \fB/usr/lib/libfoo.so\fP) or a flag
(e.g. \fB\-Wl,...\fP).  The name is never treated as a library target
name even if it happens to name one.
.sp
The \fBIMPORTED_LIBNAME\fP property is allowed only on
\fI\%imported\fP \fI\%Interface Libraries\fP
and is rejected on targets of other types (for which
the \fI\%IMPORTED_LOCATION\fP target property may be used).
.SS IMPORTED_LIBNAME_<CONFIG>
.sp
Added in version 3.8.

.sp
<CONFIG>\-specific version of \fI\%IMPORTED_LIBNAME\fP property.
.sp
Configuration names correspond to those provided by the project from
which the target is imported.
.SS IMPORTED_LINK_DEPENDENT_LIBRARIES
.sp
Dependent shared libraries of an imported shared library.
.sp
Shared libraries may be linked to other shared libraries as part of
their implementation.  On some platforms the linker searches for the
dependent libraries of shared libraries they are including in the
link.  Set this property to the list of dependent shared libraries of
an imported library.  The list should be disjoint from the list of
interface libraries in the \fI\%INTERFACE_LINK_LIBRARIES\fP property.  On
platforms requiring dependent shared libraries to be found at link
time CMake uses this list to add appropriate files or paths to the
link command line.  Ignored for non\-imported targets.
.SS IMPORTED_LINK_DEPENDENT_LIBRARIES_<CONFIG>
.sp
<CONFIG>\-specific version of \fI\%IMPORTED_LINK_DEPENDENT_LIBRARIES\fP\&.
.sp
Configuration names correspond to those provided by the project from
which the target is imported.  If set, this property completely
overrides the generic property for the named configuration.
.SS IMPORTED_LINK_INTERFACE_LANGUAGES
.sp
Languages compiled into an \fBIMPORTED\fP static library.
.sp
Set this to the list of languages of source files compiled to produce
a \fBSTATIC IMPORTED\fP library (such as \fBC\fP or \fBCXX\fP).  CMake accounts for
these languages when computing how to link a target to the imported
library.  For example, when a C executable links to an imported C++
static library CMake chooses the C++ linker to satisfy language
runtime dependencies of the static library.
.sp
This property is ignored for targets that are not \fBSTATIC\fP libraries.
This property is ignored for non\-imported targets.
.SS IMPORTED_LINK_INTERFACE_LANGUAGES_<CONFIG>
.sp
<CONFIG>\-specific version of \fI\%IMPORTED_LINK_INTERFACE_LANGUAGES\fP\&.
.sp
Configuration names correspond to those provided by the project from
which the target is imported.  If set, this property completely
overrides the generic property for the named configuration.
.SS IMPORTED_LINK_INTERFACE_LIBRARIES
.sp
Transitive link interface of an \fBIMPORTED\fP target.
.sp
Set this to the list of libraries whose interface is included when an
\fBIMPORTED\fP library target is linked to another target.  The libraries
will be included on the link line for the target.  Unlike the
\fI\%LINK_INTERFACE_LIBRARIES\fP property, this property applies to all
imported target types, including \fBSTATIC\fP libraries.  This property is
ignored for non\-imported targets.
.sp
This property is ignored if the target also has a non\-empty
\fI\%INTERFACE_LINK_LIBRARIES\fP property.
.sp
This property is deprecated.  Use \fI\%INTERFACE_LINK_LIBRARIES\fP instead.
.SS IMPORTED_LINK_INTERFACE_LIBRARIES_<CONFIG>
.sp
<CONFIG>\-specific version of \fI\%IMPORTED_LINK_INTERFACE_LIBRARIES\fP\&.
.sp
Configuration names correspond to those provided by the project from
which the target is imported.  If set, this property completely
overrides the generic property for the named configuration.
.sp
This property is ignored if the target also has a non\-empty
\fI\%INTERFACE_LINK_LIBRARIES\fP property.
.sp
This property is deprecated.  Use \fI\%INTERFACE_LINK_LIBRARIES\fP instead.
.SS IMPORTED_LINK_INTERFACE_MULTIPLICITY
.sp
Repetition count for cycles of \fBIMPORTED\fP static libraries.
.sp
This is \fI\%LINK_INTERFACE_MULTIPLICITY\fP for \fBIMPORTED\fP targets.
.SS IMPORTED_LINK_INTERFACE_MULTIPLICITY_<CONFIG>
.sp
<CONFIG>\-specific version of \fI\%IMPORTED_LINK_INTERFACE_MULTIPLICITY\fP\&.
.sp
If set, this property completely overrides the generic property for
the named configuration.
.SS IMPORTED_LOCATION
.sp
Full path to the main file on disk for an \fBIMPORTED\fP target.
.sp
Set this to the location of an \fBIMPORTED\fP target file on disk.  For
executables this is the location of the executable file.  For \fBSTATIC\fP
libraries and modules this is the location of the library or module.
For \fBSHARED\fP libraries on non\-DLL platforms this is the location of the
shared library.  For application bundles on macOS this is the location of
the executable file inside \fBContents/MacOS\fP within the bundle folder.
For frameworks on macOS this is the location of the
library file symlink just inside the framework folder.  For DLLs this
is the location of the \fB\&.dll\fP part of the library.  For \fBUNKNOWN\fP
libraries this is the location of the file to be linked.  Ignored for
non\-imported targets.
.sp
Added in version 3.28: For ordinary frameworks on Apple platforms, this may be the location of the
\fB\&.framework\fP folder itself.  For XCFrameworks, it may be the location of
the \fB\&.xcframework\fP folder, in which case any target that links against it
will get the selected library\(aqs \fBHeaders\fP directory as a usage requirement.

.sp
The \fBIMPORTED_LOCATION\fP target property may be overridden for a
given configuration \fB<CONFIG>\fP by the configuration\-specific
\fI\%IMPORTED_LOCATION_<CONFIG>\fP target property.  Furthermore,
the \fI\%MAP_IMPORTED_CONFIG_<CONFIG>\fP target property may be
used to map between a project\(aqs configurations and those of an imported
target.  If none of these is set then the name of any other configuration
listed in the \fI\%IMPORTED_CONFIGURATIONS\fP target property may be
selected and its \fI\%IMPORTED_LOCATION_<CONFIG>\fP value used.
.sp
To get the location of an imported target read one of the \fI\%LOCATION\fP
or \fI\%LOCATION_<CONFIG>\fP properties.
.sp
For platforms with import libraries (e.g. Windows, AIX or Apple) see also
\fI\%IMPORTED_IMPLIB\fP\&.
.SS IMPORTED_LOCATION_<CONFIG>
.sp
<CONFIG>\-specific version of \fI\%IMPORTED_LOCATION\fP property.
.sp
Configuration names correspond to those provided by the project from
which the target is imported.
.SS IMPORTED_NO_SONAME
.sp
Specifies that an \fBIMPORTED\fP shared library target has no \fBsoname\fP\&.
.sp
Set this property to true for an imported shared library file that has
no \fBsoname\fP field.  CMake may adjust generated link commands for some
platforms to prevent the linker from using the path to the library in
place of its missing \fBsoname\fP\&.  Ignored for non\-imported targets.
.SS IMPORTED_NO_SONAME_<CONFIG>
.sp
<CONFIG>\-specific version of \fI\%IMPORTED_NO_SONAME\fP property.
.sp
Configuration names correspond to those provided by the project from
which the target is imported.
.SS IMPORTED_OBJECTS
.sp
Added in version 3.9.

.sp
A \fI\%semicolon\-separated list\fP of absolute paths
to the object files on disk for an \fI\%imported\fP
\fI\%object library\fP\&.
.sp
Ignored for non\-imported targets.
.sp
Projects may skip \fBIMPORTED_OBJECTS\fP if the configuration\-specific
property \fI\%IMPORTED_OBJECTS_<CONFIG>\fP is set instead, except in
situations as noted in the section below.
.SS Xcode Generator Considerations
.sp
Added in version 3.20.

.sp
For Apple platforms, a project may be built for more than one architecture.
This is controlled by the \fI\%CMAKE_OSX_ARCHITECTURES\fP variable.
For all but the \fI\%Xcode\fP generator, CMake invokes compilers once
per source file and passes multiple \fB\-arch\fP flags, leading to a single
object file which will be a universal binary.  Such object files work well
when listed in the \fBIMPORTED_OBJECTS\fP of a separate CMake build, even for
the \fI\%Xcode\fP generator.  But producing such object files with the
\fI\%Xcode\fP generator is more difficult, since it invokes the compiler
once per architecture for each source file.  Unlike the other generators,
it does not generate universal object file binaries.
.sp
A further complication with the \fI\%Xcode\fP generator is that when
targeting device platforms (iOS, tvOS, visionOS or watchOS), the \fI\%Xcode\fP
generator has the ability to use either the device or simulator SDK without
needing CMake to be re\-run.  The SDK can be selected at build time.
But since some architectures can be supported by both the device and the
simulator SDKs (e.g. \fBarm64\fP with Xcode 12 or later), not all combinations
can be represented in a single universal binary.  The only solution in this
case is to have multiple object files.
.sp
\fBIMPORTED_OBJECTS\fP doesn\(aqt support generator expressions, so every file
it lists needs to be valid for every architecture and SDK.  If incorporating
object files that are not universal binaries, the path and/or file name of
each object file has to somehow encapsulate the different architectures and
SDKs.  With the \fI\%Xcode\fP generator, Xcode variables of the form
\fB$(...)\fP can be used to represent these aspects and Xcode will substitute
the appropriate values at build time.  CMake doesn\(aqt interpret these
variables and embeds them unchanged in the Xcode project file.
\fB$(CURRENT_ARCH)\fP can be used to represent the architecture, while
\fB$(EFFECTIVE_PLATFORM_NAME)\fP can be used to differentiate between SDKs.
.sp
The following shows one example of how these two variables can be used to
refer to an object file whose location depends on both the SDK and the
architecture:
.INDENT 0.0
.INDENT 3.5
.sp
.EX
add_library(someObjs OBJECT IMPORTED)

set_property(TARGET someObjs PROPERTY IMPORTED_OBJECTS
  # Quotes are required because of the ()
  \(dq/path/to/somewhere/objects$(EFFECTIVE_PLATFORM_NAME)/$(CURRENT_ARCH)/func.o\(dq
)

# Example paths:
#   /path/to/somewhere/objects\-iphoneos/arm64/func.o
#   /path/to/somewhere/objects\-iphonesimulator/x86_64/func.o
.EE
.UNINDENT
.UNINDENT
.sp
In some cases, you may want to have configuration\-specific object files
as well.  The \fB$(CONFIGURATION)\fP Xcode variable is often used for this and
can be used in conjunction with the others mentioned above:
.INDENT 0.0
.INDENT 3.5
.sp
.EX
add_library(someObjs OBJECT IMPORTED)
set_property(TARGET someObjs PROPERTY IMPORTED_OBJECTS
  \(dq/path/to/somewhere/$(CONFIGURATION)$(EFFECTIVE_PLATFORM_NAME)/$(CURRENT_ARCH)/func.o\(dq
)

# Example paths:
#   /path/to/somewhere/Release\-iphoneos/arm64/func.o
#   /path/to/somewhere/Debug\-iphonesimulator/x86_64/func.o
.EE
.UNINDENT
.UNINDENT
.sp
When any Xcode variable is used, CMake is not able to fully evaluate the
path(s) at configure time.  One consequence of this is that the
configuration\-specific \fI\%IMPORTED_OBJECTS_<CONFIG>\fP properties cannot
be used, since CMake cannot determine whether an object file exists at a
particular \fB<CONFIG>\fP location.  The \fBIMPORTED_OBJECTS\fP property must be
used for these situations and the configuration\-specific aspects of the path
should be handled by the \fB$(CONFIGURATION)\fP Xcode variable.
.SS IMPORTED_OBJECTS_<CONFIG>
.sp
Added in version 3.9.

.sp
\fB<CONFIG>\fP\-specific version of \fI\%IMPORTED_OBJECTS\fP property.
.sp
Configuration names correspond to those provided by the project from
which the target is imported.
.SS Xcode Generator Considerations
.sp
Do not use this \fB<CONFIG>\fP\-specific property if you need to use
\fI\%Xcode\fP variables like \fB$(CURRENT_ARCH)\fP or
\fB$(EFFECTIVE_PLATFORM_NAME)\fP in the value.  The \fB<CONFIG>\fP\-specific
properties will be ignored in such cases because CMake cannot determine
whether a file exists at the configuration\-specific path at configuration
time.  For such cases, use \fI\%IMPORTED_OBJECTS\fP instead.
.SS IMPORTED_SONAME
.sp
The \fBsoname\fP of an \fBIMPORTED\fP target of shared library type.
.sp
Set this to the \fBsoname\fP embedded in an imported shared library.  This
is meaningful only on platforms supporting the feature.  Ignored for
non\-imported targets.
.SS IMPORTED_SONAME_<CONFIG>
.sp
<CONFIG>\-specific version of \fI\%IMPORTED_SONAME\fP property.
.sp
Configuration names correspond to those provided by the project from
which the target is imported.
.SS IMPORT_PREFIX
.sp
What comes before the import library name.
.sp
Similar to the target property \fI\%PREFIX\fP, but used for import libraries
(typically corresponding to a \fBDLL\fP) instead of regular libraries.  A
target property that can be set to override the prefix (such as \fBlib\fP)
on an import library name.
.SS IMPORT_SUFFIX
.sp
What comes after the import library name.
.sp
Similar to the target property \fI\%SUFFIX\fP, but used
for import libraries (typically corresponding to a \fBDLL\fP) instead of
regular libraries.  A target property that can be set to override
the suffix (such as \fB\&.lib\fP) on an import library name.
.SS INCLUDE_DIRECTORIES
.sp
List of preprocessor include file search directories.
.sp
This property specifies the list of directories given so far to the
\fI\%target_include_directories()\fP command.  In addition to accepting
values from that command, values may be set directly on any
target using the \fI\%set_property()\fP command.  A target gets its
initial value for this property from the value of the
\fI\%INCLUDE_DIRECTORIES\fP directory property.  Both directory and
target property values are adjusted by calls to the
\fI\%include_directories()\fP command.
.sp
The value of this property is used by the generators to set the include
paths for the compiler.
.sp
Relative paths should not be added to this property directly. Use one of
the commands above instead to handle relative paths.
.sp
Contents of \fBINCLUDE_DIRECTORIES\fP may use \fI\%cmake\-generator\-expressions(7)\fP with
the syntax \fB$<...>\fP\&.  See the \fI\%cmake\-generator\-expressions(7)\fP
manual for available expressions.  See the \fI\%cmake\-buildsystem(7)\fP
manual for more on defining buildsystem properties.
.SS INSTALL_NAME_DIR
.sp
Directory name for installed targets on Apple platforms.
.sp
\fBINSTALL_NAME_DIR\fP is a string specifying the directory portion of the
\(dqinstall_name\(dq field of shared libraries on Apple platforms for
installed targets.  When not set, the default directory used is determined
by \fI\%MACOSX_RPATH\fP\&.  If the \fI\%BUILD_WITH_INSTALL_NAME_DIR\fP
property is set, this will be used already in the build tree.
Policies \fI\%CMP0068\fP and \fI\%CMP0042\fP are also relevant.
.sp
This property is initialized by the value of the variable
\fI\%CMAKE_INSTALL_NAME_DIR\fP if it is set when a target is
created.
.sp
This property supports \fI\%generator expressions\fP\&.
In particular, the \fI\%$<INSTALL_PREFIX>\fP generator expression can be
used to set the directory relative to the install\-time prefix.
.sp
On platforms that support runtime paths (\fBRPATH\fP), refer to the
\fI\%INSTALL_RPATH\fP target property.
Under Windows, the \fI\%TARGET_RUNTIME_DLLS\fP generator expression is related.
.SS INSTALL_REMOVE_ENVIRONMENT_RPATH
.sp
Added in version 3.16.

.sp
Controls whether toolchain\-defined rpaths should be removed during installation.
.sp
When a target is being installed, CMake may need to rewrite its rpath
information.  This occurs when the install rpath (as specified by the
\fI\%INSTALL_RPATH\fP target property) has different contents to the rpath
that the target was built with.  Some toolchains insert their own rpath
contents into the binary as part of the build.  By default, CMake will
preserve those extra inserted contents in the install rpath.  For those
scenarios where such toolchain\-inserted entries need to be discarded during
install, set the \fBINSTALL_REMOVE_ENVIRONMENT_RPATH\fP target property to true.
.sp
This property is initialized by the value of
\fI\%CMAKE_INSTALL_REMOVE_ENVIRONMENT_RPATH\fP when the target is created.
.SS INSTALL_RPATH
.sp
The rpath to use for installed targets.
.sp
By default, the install rpath is empty. It can be set using this property,
which is a semicolon\-separated list specifying the rpath to use in installed
targets (for platforms that support it).  This property is initialized
by the value of the variable \fI\%CMAKE_INSTALL_RPATH\fP if it is set
when a target is created.
Beside setting the install rpath manually, using the
\fI\%INSTALL_RPATH_USE_LINK_PATH\fP target property it can also be
generated automatically by CMake.
.sp
Normally CMake uses the build tree for the RPATH when building executables
etc on systems that use RPATH, see the \fI\%BUILD_RPATH\fP target
property. When the software is installed
the targets are edited (or relinked) by CMake (see
\fI\%CMAKE_NO_BUILTIN_CHRPATH\fP) to have the install RPATH.
This editing during installation can be avoided via
the \fI\%BUILD_WITH_INSTALL_RPATH\fP target property.
.sp
For handling toolchain\-dependent RPATH entries the
\fI\%INSTALL_REMOVE_ENVIRONMENT_RPATH\fP can be used.
Runtime paths can be disabled completely via the \fI\%CMAKE_SKIP_RPATH\fP
variable.
.sp
Because the rpath may contain \fB${ORIGIN}\fP, which coincides with CMake syntax,
the contents of \fBINSTALL_RPATH\fP are properly escaped in the
\fBcmake_install.cmake\fP script (see policy \fI\%CMP0095\fP\&.)
.sp
This property supports
\fI\%generator expressions\fP\&.
.sp
On Apple platforms, refer to the \fI\%INSTALL_NAME_DIR\fP target property.
Under Windows, the \fI\%TARGET_RUNTIME_DLLS\fP generator expression is related.
.SS INSTALL_RPATH_USE_LINK_PATH
.sp
Add paths to linker search and installed rpath.
.sp
\fBINSTALL_RPATH_USE_LINK_PATH\fP is a boolean that if set to \fBTRUE\fP
will append to the runtime search path (rpath) of installed binaries
any directories outside the project that are in the linker search path or
contain linked library files.  The directories are appended after the
value of the \fI\%INSTALL_RPATH\fP target property.
.sp
This property is initialized by the value of the variable
\fI\%CMAKE_INSTALL_RPATH_USE_LINK_PATH\fP if it is set when a target is
created.
.SS INTERFACE_AUTOMOC_MACRO_NAMES
.sp
Added in version 3.27.

.sp
A \fI\%semicolon\-separated list\fP of macro names for
\fI\%AUTOMOC\fP to be propagated to consumers.
.sp
When a target with \fI\%AUTOMOC\fP enabled links to a library that sets
\fBINTERFACE_AUTOMOC_MACRO_NAMES\fP, the target inherits the listed macro names
and merges them with those specified in its own \fI\%AUTOMOC_MACRO_NAMES\fP
property.  The target will then automatically generate MOC files for source
files that contain the inherited macro names too, not just the macro names
specified in its own \fI\%AUTOMOC_MACRO_NAMES\fP property.
.sp
By default \fBINTERFACE_AUTOMOC_MACRO_NAMES\fP is empty.
.sp
See the \fI\%cmake\-qt(7)\fP manual for more information on using CMake
with Qt.
.SS Example 1
.sp
In this example, \fBmyapp\fP inherits the macro names \fBSTATIC_LIB_1\fP and
\fBSTATIC_LIB_2\fP from \fBstatic_lib\fP\&.  The \fBmoc\fP tool will then automatically
be run on any of the \fBmyapp\fP sources which contain \fBSTATIC_LIB_1\fP or
\fBSTATIC_LIB_2\fP\&.
.INDENT 0.0
.INDENT 3.5
.sp
.EX
set(AUTOMOC ON)
add_executable(myapp main.cpp)
target_link_libraries(myapp PRIVATE static_lib)

add_library(static_lib STATIC static.cpp)
set_property(TARGET static_lib PROPERTY
  INTERFACE_AUTOMOC_MACRO_NAMES \(dqSTATIC_LIB_1;STATIC_LIB_2\(dq
)
.EE
.UNINDENT
.UNINDENT
.SS Example 2
.sp
In this example, the \fBINTERFACE_AUTOMOC_MACRO_NAMES\fP target property of the
various \fB*_deep_lib\fP libraries will propagate to \fBshared_lib\fP,
\fBstatic_lib\fP and \fBinterface_lib\fP\&.  Because the linking relationships are
specified as \fBPUBLIC\fP and \fBINTERFACE\fP, those macro names will also further
propagate transitively up to \fBapp\fP\&.
.INDENT 0.0
.INDENT 3.5
.sp
.EX
set(AUTOMOC ON)

add_library(shared_deep_lib SHARED deep_lib.cpp)
add_library(static_deep_lib STATIC deep_lib.cpp)
add_library(interface_deep_lib INTERFACE)

set_property(TARGET shared_deep_lib PROPERTY
  INTERFACE_AUTOMOC_MACRO_NAMES \(dqSHARED_LINK_LIB\(dq
)
set_property(TARGET static_deep_lib PROPERTY
  INTERFACE_AUTOMOC_MACRO_NAMES \(dqSTATIC_LINK_LIB\(dq
)
set_property(TARGET interface_deep_lib PROPERTY
  INTERFACE_AUTOMOC_MACRO_NAMES \(dqINTERFACE_LINK_LIB\(dq
)

add_library(shared_lib SHARED lib.cpp)
add_library(static_lib STATIC lib.cpp)
add_library(interface_lib INTERFACE)

# PUBLIC and INTERFACE here ensure the macro names propagate to any
# consumers of shared_lib, static_lib or interface_lib too
target_link_libraries(shared_lib PUBLIC shared_deep_lib)
target_link_libraries(static_lib PUBLIC static_deep_lib)
target_link_libraries(interface_lib INTERFACE interface_deep_lib)

# This consumer will receive all three of the above custom macro names as
# transitive usage requirements
add_executable(app main.cpp)
target_link_libraries(app PRIVATE shared_lib static_lib interface_lib)
.EE
.UNINDENT
.UNINDENT
.sp
In the above:
.INDENT 0.0
.IP \(bu 2
\fBshared_lib\fP sources will be processed by \fBmoc\fP if they contain
\fBSHARED_LINK_LIB\fP\&.
.IP \(bu 2
\fBstatic_lib\fP sources will be processed by \fBmoc\fP if they contain
\fBSTATIC_LINK_LIB\fP\&.
.IP \(bu 2
\fBapp\fP sources will be processed by \fBmoc\fP if they contain
\fBSHARED_LINK_LIB\fP, \fBSTATIC_LINK_LIB\fP or \fBINTERFACE_LINK_LIB\fP\&.
.UNINDENT
.SS INTERFACE_AUTOUIC_OPTIONS
.sp
Added in version 3.0.

.sp
List of interface options to pass to uic.
.sp
Targets may populate this property to publish the options
required to use when invoking \fBuic\fP\&.  Consuming targets can add entries to their
own \fI\%AUTOUIC_OPTIONS\fP property such as
\fB$<TARGET_PROPERTY:foo,INTERFACE_AUTOUIC_OPTIONS>\fP to use the uic options
specified in the interface of \fBfoo\fP\&. This is done automatically by
the \fI\%target_link_libraries()\fP command.
.sp
This property supports generator expressions.  See the
\fI\%cmake\-generator\-expressions(7)\fP manual for available expressions.
.SS INTERFACE_COMPILE_DEFINITIONS
.sp
List of public compile definitions requirements for a library.
.sp
Targets may populate this property to publish the compile definitions
required to compile against the headers for the target.  The \fI\%target_compile_definitions()\fP
command populates this property with values given to the \fBPUBLIC\fP and
\fBINTERFACE\fP keywords.  Projects may also get and set the property directly.
.sp
When target dependencies are specified using \fI\%target_link_libraries()\fP,
CMake will read this property from all target dependencies to determine the
build properties of the consumer.
.sp
Contents of \fBINTERFACE_COMPILE_DEFINITIONS\fP may use \(dqgenerator expressions\(dq
with the syntax \fB$<...>\fP\&.  See the \fI\%cmake\-generator\-expressions(7)\fP
manual for available expressions.  See the \fI\%cmake\-buildsystem(7)\fP
\-manual for more on defining buildsystem properties.
.SS INTERFACE_COMPILE_FEATURES
.sp
Added in version 3.1.

.sp
List of public compile features requirements for a library.
.sp
Targets may populate this property to publish the compile features
required to compile against the headers for the target.  The \fI\%target_compile_features()\fP
command populates this property with values given to the \fBPUBLIC\fP and
\fBINTERFACE\fP keywords.  Projects may also get and set the property directly.
.sp
When target dependencies are specified using \fI\%target_link_libraries()\fP,
CMake will read this property from all target dependencies to determine the
build properties of the consumer.
.sp
Contents of \fBINTERFACE_COMPILE_FEATURES\fP may use \(dqgenerator expressions\(dq
with the syntax \fB$<...>\fP\&.  See the \fI\%cmake\-generator\-expressions(7)\fP
manual for available expressions.  See the \fI\%cmake\-buildsystem(7)\fP
\-manual for more on defining buildsystem properties.
.sp
See the \fI\%cmake\-compile\-features(7)\fP manual for information on compile
features and a list of supported compilers.
.SS INTERFACE_COMPILE_OPTIONS
.sp
List of public compile options requirements for a library.
.sp
Targets may populate this property to publish the compile options
required to compile against the headers for the target.  The \fI\%target_compile_options()\fP
command populates this property with values given to the \fBPUBLIC\fP and
\fBINTERFACE\fP keywords.  Projects may also get and set the property directly.
.sp
When target dependencies are specified using \fI\%target_link_libraries()\fP,
CMake will read this property from all target dependencies to determine the
build properties of the consumer.
.sp
Contents of \fBINTERFACE_COMPILE_OPTIONS\fP may use \(dqgenerator expressions\(dq
with the syntax \fB$<...>\fP\&.  See the \fI\%cmake\-generator\-expressions(7)\fP
manual for available expressions.  See the \fI\%cmake\-buildsystem(7)\fP
\-manual for more on defining buildsystem properties.
.SS INTERFACE_CXX_MODULE_SETS
.sp
Added in version 3.28.

.sp
Read\-only list of the target\(aqs \fBPUBLIC\fP C++ module sets (i.e. all file sets
with the type \fBCXX_MODULES\fP). Files listed in these C++ module sets can be
installed with \fI\%install(TARGETS)\fP and exported with
\fI\%install(EXPORT)\fP and \fI\%export()\fP\&.
.sp
C++ module sets may be defined using the \fI\%target_sources()\fP command
\fBFILE_SET\fP option with type \fBCXX_MODULES\fP\&.
.sp
See also \fI\%CXX_MODULE_SETS\fP\&.
.SS INTERFACE_HEADER_SETS
.sp
Added in version 3.23.

.sp
Read\-only list of the target\(aqs \fBINTERFACE\fP and \fBPUBLIC\fP header sets (i.e.
all file sets with the type \fBHEADERS\fP). Files listed in these header sets
can be installed with \fI\%install(TARGETS)\fP and exported with
\fI\%install(EXPORT)\fP and \fI\%export()\fP\&.
.sp
Header sets may be defined using the \fI\%target_sources()\fP command
\fBFILE_SET\fP option with type \fBHEADERS\fP\&.
.sp
See also \fI\%HEADER_SETS\fP\&.
.SS INTERFACE_HEADER_SETS_TO_VERIFY
.sp
Added in version 3.24.

.sp
Used to specify which \fBPUBLIC\fP and \fBINTERFACE\fP header sets of a target
should be verified.
.sp
This property contains a semicolon\-separated list of header sets which
should be verified if \fI\%VERIFY_INTERFACE_HEADER_SETS\fP is set to
\fBTRUE\fP\&. If the list is empty, all \fBPUBLIC\fP and \fBINTERFACE\fP header sets
are verified. (If the project does not want to verify any header sets on the
target, simply set \fI\%VERIFY_INTERFACE_HEADER_SETS\fP to \fBFALSE\fP\&.)
.SS INTERFACE_INCLUDE_DIRECTORIES
.sp
List of public include directories requirements for a library.
.sp
Targets may populate this property to publish the include directories
required to compile against the headers for the target.  The \fI\%target_include_directories()\fP
command populates this property with values given to the \fBPUBLIC\fP and
\fBINTERFACE\fP keywords.  Projects may also get and set the property directly.
.sp
When target dependencies are specified using \fI\%target_link_libraries()\fP,
CMake will read this property from all target dependencies to determine the
build properties of the consumer.
.sp
Contents of \fBINTERFACE_INCLUDE_DIRECTORIES\fP may use \(dqgenerator expressions\(dq
with the syntax \fB$<...>\fP\&.  See the \fI\%cmake\-generator\-expressions(7)\fP
manual for available expressions.  See the \fI\%cmake\-buildsystem(7)\fP
\-manual for more on defining buildsystem properties.
.sp
Include directories usage requirements commonly differ between the build\-tree
and the install\-tree.  The \fBBUILD_INTERFACE\fP and \fBINSTALL_INTERFACE\fP
generator expressions can be used to describe separate usage requirements
based on the usage location.  Relative paths are allowed within the
\fBINSTALL_INTERFACE\fP expression and are interpreted relative to the
installation prefix.  For example:
.INDENT 0.0
.INDENT 3.5
.sp
.EX
target_include_directories(mylib INTERFACE
  $<BUILD_INTERFACE:${CMAKE_CURRENT_SOURCE_DIR}/include/mylib>
  $<INSTALL_INTERFACE:include/mylib>  # <prefix>/include/mylib
)
.EE
.UNINDENT
.UNINDENT
.SS Creating Relocatable Packages
.sp
Note that it is not advisable to populate the \fI\%INSTALL_INTERFACE\fP of
the \fBINTERFACE_INCLUDE_DIRECTORIES\fP of a target with absolute paths to the include
directories of dependencies.  That would hard\-code into installed packages
the include directory paths for dependencies
\fBas found on the machine the package was made on\fP\&.
.sp
The \fI\%INSTALL_INTERFACE\fP of the \fBINTERFACE_INCLUDE_DIRECTORIES\fP is only
suitable for specifying the required include directories for headers
provided with the target itself, not those provided by the transitive
dependencies listed in its \fI\%INTERFACE_LINK_LIBRARIES\fP target
property.  Those dependencies should themselves be targets that specify
their own header locations in \fBINTERFACE_INCLUDE_DIRECTORIES\fP\&.
.sp
See the \fI\%Creating Relocatable Packages\fP section of the
\fI\%cmake\-packages(7)\fP manual for discussion of additional care
that must be taken when specifying usage requirements while creating
packages for redistribution.
.SS INTERFACE_LINK_DEPENDS
.sp
Added in version 3.13.

.sp
Additional public interface files on which a target binary depends for linking.
.sp
This property is supported only by \fI\%Ninja\fP and
\fI\%Makefile Generators\fP\&.
It is intended to specify dependencies on \(dqlinker scripts\(dq for
custom Makefile link rules.
.sp
When target dependencies are specified using \fI\%target_link_libraries()\fP,
CMake will read this property from all target dependencies to determine the
build properties of the consumer.
.sp
Contents of \fBINTERFACE_LINK_DEPENDS\fP may use \(dqgenerator expressions\(dq
with the syntax \fB$<...>\fP\&.  See the \fI\%cmake\-generator\-expressions(7)\fP
manual for available expressions.  See the \fI\%cmake\-buildsystem(7)\fP
\-manual for more on defining buildsystem properties.
.sp
Link dependency files usage requirements commonly differ between the build\-tree
and the install\-tree.  The \fBBUILD_INTERFACE\fP and \fBINSTALL_INTERFACE\fP
generator expressions can be used to describe separate usage requirements
based on the usage location.  Relative paths are allowed within the
\fBINSTALL_INTERFACE\fP expression and are interpreted relative to the
installation prefix.  For example:
.INDENT 0.0
.INDENT 3.5
.sp
.EX
set_property(TARGET mylib PROPERTY INTERFACE_LINK_DEPENDS
  $<BUILD_INTERFACE:${CMAKE_CURRENT_SOURCE_DIR}/mylinkscript>
  $<INSTALL_INTERFACE:mylinkscript>  # <prefix>/mylinkscript
)
.EE
.UNINDENT
.UNINDENT
.SS INTERFACE_LINK_DIRECTORIES
.sp
Added in version 3.13.

.sp
List of public link directories requirements for a library.
.sp
Targets may populate this property to publish the link directories
required to compile against the headers for the target.  The \fI\%target_link_directories()\fP
command populates this property with values given to the \fBPUBLIC\fP and
\fBINTERFACE\fP keywords.  Projects may also get and set the property directly.
.sp
When target dependencies are specified using \fI\%target_link_libraries()\fP,
CMake will read this property from all target dependencies to determine the
build properties of the consumer.
.sp
Contents of \fBINTERFACE_LINK_DIRECTORIES\fP may use \(dqgenerator expressions\(dq
with the syntax \fB$<...>\fP\&.  See the \fI\%cmake\-generator\-expressions(7)\fP
manual for available expressions.  See the \fI\%cmake\-buildsystem(7)\fP
\-manual for more on defining buildsystem properties.
.SS INTERFACE_LINK_LIBRARIES
.sp
List public interface libraries for a library.
.sp
This property contains the list of transitive link dependencies.  When
the target is linked into another target using the
\fI\%target_link_libraries()\fP command, the libraries listed (and
recursively their link interface libraries) will be provided to the
other target also.  This property is overridden by the
\fI\%LINK_INTERFACE_LIBRARIES\fP or
\fI\%LINK_INTERFACE_LIBRARIES_<CONFIG>\fP property if policy
\fI\%CMP0022\fP is \fBOLD\fP or unset.
.sp
The value of this property is used by the generators when constructing
the link rule for a dependent target.  A dependent target\(aqs direct
link dependencies, specified by its \fI\%LINK_LIBRARIES\fP target
property, are linked first, followed by indirect dependencies from the
transitive closure of the direct dependencies\(aq
\fBINTERFACE_LINK_LIBRARIES\fP properties.  See policy \fI\%CMP0022\fP\&.
.sp
Contents of \fBINTERFACE_LINK_LIBRARIES\fP may use \(dqgenerator expressions\(dq
with the syntax \fB$<...>\fP\&.  See the \fI\%cmake\-generator\-expressions(7)\fP
manual for available expressions.  See the \fI\%cmake\-buildsystem(7)\fP
manual for more on defining buildsystem properties.
.sp
\fBNOTE:\fP
.INDENT 0.0
.INDENT 3.5
A call to \fI\%target_link_libraries(<target> ...)\fP may update this
property on \fB<target>\fP\&.  If \fB<target>\fP was not created in the same
directory as the call then \fI\%target_link_libraries()\fP will wrap each
entry with the form \fB::@(directory\-id);...;::@\fP, where the \fB::@\fP is
literal and the \fB(directory\-id)\fP is unspecified.
This tells the generators that the named libraries must be looked up in
the scope of the caller rather than in the scope in which the
\fB<target>\fP was created.  Valid directory ids are stripped on export
by the \fI\%install(EXPORT)\fP and \fI\%export()\fP commands.
.UNINDENT
.UNINDENT
.sp
\fBINTERFACE_LINK_LIBRARIES\fP adds transitive link dependencies for a
target\(aqs dependents.  In advanced use cases, one may update the
direct link dependencies of a target\(aqs dependents by using the
\fI\%INTERFACE_LINK_LIBRARIES_DIRECT\fP and
\fI\%INTERFACE_LINK_LIBRARIES_DIRECT_EXCLUDE\fP target properties.
.SS Handling Compiler Driver Differences
.sp
Added in version 4.0.

.sp
To pass options to the linker tool, each compiler driver has its own syntax.
The \fBLINKER:\fP prefix and \fB,\fP separator can be used to specify, in a portable
way, options to pass to the linker tool. \fBLINKER:\fP is replaced by the
appropriate driver option and \fB,\fP by the appropriate driver separator.
The driver prefix and driver separator are given by the values of the
\fI\%CMAKE_<LANG>_LINKER_WRAPPER_FLAG\fP and
\fI\%CMAKE_<LANG>_LINKER_WRAPPER_FLAG_SEP\fP variables.
.sp
For example, \fB\(dqLINKER:\-z,defs\(dq\fP becomes \fB\-Xlinker \-z \-Xlinker defs\fP for
\fBClang\fP and \fB\-Wl,\-z,defs\fP for \fBGNU GCC\fP\&.
.sp
The \fBLINKER:\fP prefix supports, as an alternative syntax, specification of
arguments using the \fBSHELL:\fP prefix and space as separator. The previous
example then becomes \fB\(dqLINKER:SHELL:\-z defs\(dq\fP\&.
.sp
\fBNOTE:\fP
.INDENT 0.0
.INDENT 3.5
Specifying the \fBSHELL:\fP prefix anywhere other than at the beginning of the
\fBLINKER:\fP prefix is not supported.
.UNINDENT
.UNINDENT
.SS Creating Relocatable Packages
.sp
Note that it is not advisable to populate the
\fBINTERFACE_LINK_LIBRARIES\fP of a target with absolute paths to dependencies.
That would hard\-code into installed packages the library file paths
for dependencies \fBas found on the machine the package was made on\fP\&.
.sp
See the \fI\%Creating Relocatable Packages\fP section of the
\fI\%cmake\-packages(7)\fP manual for discussion of additional care
that must be taken when specifying usage requirements while creating
packages for redistribution.
.SS INTERFACE_LINK_LIBRARIES_DIRECT
.sp
Added in version 3.24.

.sp
List of libraries that consumers of this library should treat
as direct link dependencies.
.sp
This target property may be set to \fIinclude\fP items in a dependent
target\(aqs final set of direct link dependencies.  See the
\fI\%INTERFACE_LINK_LIBRARIES_DIRECT_EXCLUDE\fP target property
to exclude items.
.sp
The initial set of a dependent target\(aqs direct link dependencies is
specified by its \fI\%LINK_LIBRARIES\fP target property.  Indirect
link dependencies are specified by the transitive closure of the direct
link dependencies\(aq \fI\%INTERFACE_LINK_LIBRARIES\fP properties.
Any link dependency may specify additional direct link dependencies
using the \fBINTERFACE_LINK_LIBRARIES_DIRECT\fP target property.
The set of direct link dependencies is then filtered to exclude items named
by any dependency\(aqs \fI\%INTERFACE_LINK_LIBRARIES_DIRECT_EXCLUDE\fP
target property.
.sp
The value of \fBINTERFACE_LINK_LIBRARIES_DIRECT\fP may use
\fI\%generator expressions\fP\&.
.sp
\fBNOTE:\fP
.INDENT 0.0
.INDENT 3.5
The \fBINTERFACE_LINK_LIBRARIES_DIRECT\fP target property is intended for
advanced use cases such as injection of static plugins into a consuming
executable.  It should not be used as a substitute for organizing
normal calls to \fI\%target_link_libraries()\fP\&.
.UNINDENT
.UNINDENT
.SS Direct Link Dependencies as Usage Requirements
.sp
The \fBINTERFACE_LINK_LIBRARIES_DIRECT\fP and
\fBINTERFACE_LINK_LIBRARIES_DIRECT_EXCLUDE\fP target properties
are \fI\%usage requirements\fP\&.
Their effects propagate to dependent targets transitively, and can
therefore affect the direct link dependencies of every target in a
chain of dependent libraries.  Whenever some library target \fBX\fP links
to another library target \fBY\fP whose direct or transitive usage
requirements contain \fBINTERFACE_LINK_LIBRARIES_DIRECT\fP or
\fBINTERFACE_LINK_LIBRARIES_DIRECT_EXCLUDE\fP, the properties may affect
\fBX\fP\(aqs list of direct link dependencies:
.INDENT 0.0
.IP \(bu 2
If \fBX\fP is a shared library or executable, its dependencies are linked.
They also affect the usage requirements with which \fBX\fP\(aqs sources are
compiled.
.IP \(bu 2
If \fBX\fP is a static library or object library, it does not actually
link, so its dependencies at most affect the usage requirements with
which \fBX\fP\(aqs sources are compiled.
.UNINDENT
.sp
The properties may also affect the list of direct link dependencies
on \fBX\fP\(aqs dependents:
.INDENT 0.0
.IP \(bu 2
If \fBX\fP links \fBY\fP publicly:
.INDENT 2.0
.INDENT 3.5
.sp
.EX
target_link_libraries(X PUBLIC Y)
.EE
.UNINDENT
.UNINDENT
.sp
then \fBY\fP is placed in \fBX\fP\(aqs \fI\%INTERFACE_LINK_LIBRARIES\fP,
so \fBY\fP\(aqs usage requirements, including \fBINTERFACE_LINK_LIBRARIES_DIRECT\fP,
\fBINTERFACE_LINK_LIBRARIES_DIRECT_EXCLUDE\fP, and the usage requirements
declared by the direct link dependencies they add, are propagated to
\fBX\fP\(aqs dependents.
.IP \(bu 2
If \fBX\fP is a static library or object library, and links \fBY\fP privately:
.INDENT 2.0
.INDENT 3.5
.sp
.EX
target_link_libraries(X PRIVATE Y)
.EE
.UNINDENT
.UNINDENT
.sp
then \fB$<LINK_ONLY:Y>\fP is placed in \fBX\fP\(aqs
\fI\%INTERFACE_LINK_LIBRARIES\fP\&.  \fBY\fP\(aqs linking requirements,
including \fBINTERFACE_LINK_LIBRARIES_DIRECT\fP,
\fBINTERFACE_LINK_LIBRARIES_DIRECT_EXCLUDE\fP, and the transitive link
dependencies declared by the direct link dependencies they add, are
propagated to \fBX\fP\(aqs dependents.  However, \fBY\fP\(aqs non\-linking
usage requirements are blocked by the \fI\%LINK_ONLY\fP generator
expression, and are not propagated to \fBX\fP\(aqs dependents.
.IP \(bu 2
If \fBX\fP is a shared library or executable, and links \fBY\fP privately:
.INDENT 2.0
.INDENT 3.5
.sp
.EX
target_link_libraries(X PRIVATE Y)
.EE
.UNINDENT
.UNINDENT
.sp
then \fBY\fP is not placed in \fBX\fP\(aqs \fI\%INTERFACE_LINK_LIBRARIES\fP,
so \fBY\fP\(aqs usage requirements, even \fBINTERFACE_LINK_LIBRARIES_DIRECT\fP
and \fBINTERFACE_LINK_LIBRARIES_DIRECT_EXCLUDE\fP, are not propagated to
\fBX\fP\(aqs dependents.
.IP \(bu 2
In all cases, the content of \fBX\fP\(aqs \fI\%INTERFACE_LINK_LIBRARIES\fP
is not affected by \fBY\fP\(aqs \fBINTERFACE_LINK_LIBRARIES_DIRECT\fP or
\fBINTERFACE_LINK_LIBRARIES_DIRECT_EXCLUDE\fP\&.
.UNINDENT
.sp
One may limit the effects of \fBINTERFACE_LINK_LIBRARIES_DIRECT\fP and
\fBINTERFACE_LINK_LIBRARIES_DIRECT_EXCLUDE\fP to a subset of dependent
targets by using the \fI\%TARGET_PROPERTY\fP generator expression.
For example, to limit the effects to executable targets, use an
entry of the form:
.INDENT 0.0
.INDENT 3.5
.sp
.EX
\(dq$<$<STREQUAL:$<TARGET_PROPERTY:TYPE>,EXECUTABLE>:...>\(dq
.EE
.UNINDENT
.UNINDENT
.sp
Similarly, to limit the effects to specific targets, use an entry
of the form:
.INDENT 0.0
.INDENT 3.5
.sp
.EX
\(dq$<$<BOOL:$<TARGET_PROPERTY:USE_IT>>:...>\(dq
.EE
.UNINDENT
.UNINDENT
.sp
This entry will only affect targets that set their \fBUSE_IT\fP
target property to a true value.
.SS Direct Link Dependency Ordering
.sp
The list of direct link dependencies for a target is computed from an
initial ordered list in its \fI\%LINK_LIBRARIES\fP target property.
For each item, additional direct link dependencies are discovered from
its direct and transitive \fBINTERFACE_LINK_LIBRARIES_DIRECT\fP usage
requirements.  Each discovered item is injected before the item that
specified it.  However, a discovered item is added at most once,
and only if it did not appear anywhere in the initial list.
This gives \fI\%LINK_LIBRARIES\fP control over ordering of
those direct link dependencies that it explicitly specifies.
.sp
Once all direct link dependencies have been collected, items named by
all of their \fI\%INTERFACE_LINK_LIBRARIES_DIRECT_EXCLUDE\fP
usage requirements are removed from the final list.  This does not
affect the order of the items that remain.
.SS Example: Static Plugins
.sp
Consider a static library \fBFoo\fP that provides a static plugin
\fBFooPlugin\fP to consuming application executables, where the
implementation of the plugin depends on \fBFoo\fP and other things.
In this case, the application should link to \fBFooPlugin\fP directly,
before \fBFoo\fP\&.  However, the application author only knows about \fBFoo\fP\&.
We can express this as follows:
.INDENT 0.0
.INDENT 3.5
.sp
.EX
# Core library used by other components.
add_library(Core STATIC core.cpp)

# Foo is a static library for use by applications.
# Implementation of Foo depends on Core.
add_library(Foo STATIC foo.cpp foo_plugin_helper.cpp)
target_link_libraries(Foo PRIVATE Core)

# Extra parts of Foo for use by its static plugins.
# Implementation of Foo\(aqs extra parts depends on both Core and Foo.
add_library(FooExtras STATIC foo_extras.cpp)
target_link_libraries(FooExtras PRIVATE Core Foo)

# The Foo library has an associated static plugin
# that should be linked into the final executable.
# Implementation of the plugin depends on Core, Foo, and FooExtras.
add_library(FooPlugin STATIC foo_plugin.cpp)
target_link_libraries(FooPlugin PRIVATE Core Foo FooExtras)

# An app that links Foo should link Foo\(aqs plugin directly.
set_property(TARGET Foo PROPERTY INTERFACE_LINK_LIBRARIES_DIRECT FooPlugin)

# An app does not need to link Foo directly because the plugin links it.
set_property(TARGET Foo PROPERTY INTERFACE_LINK_LIBRARIES_DIRECT_EXCLUDE Foo)
.EE
.UNINDENT
.UNINDENT
.sp
An application \fBapp\fP only needs to specify that it links to \fBFoo\fP:
.INDENT 0.0
.INDENT 3.5
.sp
.EX
add_executable(app main.cpp)
target_link_libraries(app PRIVATE Foo)
.EE
.UNINDENT
.UNINDENT
.sp
The \fBINTERFACE_LINK_LIBRARIES_DIRECT\fP target property on \fBFoo\fP tells
CMake to pretend that \fBapp\fP also links directly to \fBFooPlugin\fP\&.
The \fBINTERFACE_LINK_LIBRARIES_DIRECT_EXCLUDE\fP target property on \fBFoo\fP
tells CMake to pretend that \fBapp\fP did \fInot\fP link directly to \fBFoo\fP\&.
Instead, \fBFoo\fP will be linked as a dependency of \fBFooPlugin\fP\&.  The
final link line for \fBapp\fP will link the libraries in the following
order:
.INDENT 0.0
.IP \(bu 2
\fBFooPlugin\fP as a direct link dependency of \fBapp\fP
(via \fBFoo\fP\(aqs usage requirements).
.IP \(bu 2
\fBFooExtras\fP as a dependency of \fBFooPlugin\fP\&.
.IP \(bu 2
\fBFoo\fP as a dependency of \fBFooPlugin\fP and \fBFooExtras\fP\&.
.IP \(bu 2
\fBCore\fP as a dependency of \fBFooPlugin\fP, \fBFooExtras\fP, and \fBFoo\fP\&.
.UNINDENT
.sp
Note that without the \fBINTERFACE_LINK_LIBRARIES_DIRECT_EXCLUDE\fP target
property, \fBFoo\fP would be linked twice: once as a direct dependency
of \fBapp\fP, and once as a dependency of \fBFooPlugin\fP\&.
.SS Example: Opt\-In Static Plugins
.sp
In the above \fI\%Example: Static Plugins\fP, the \fBapp\fP executable specifies
that it links directly to \fBFoo\fP\&.  In a real application, there might
be an intermediate library:
.INDENT 0.0
.INDENT 3.5
.sp
.EX
add_library(app_impl STATIC app_impl.cpp)
target_link_libraries(app_impl PRIVATE Foo)

add_executable(app main.cpp)
target_link_libraries(app PRIVATE app_impl)
.EE
.UNINDENT
.UNINDENT
.sp
In this case we do not want \fBFoo\fP\(aqs \fBINTERFACE_LINK_LIBRARIES_DIRECT\fP
and \fBINTERFACE_LINK_LIBRARIES_DIRECT_EXCLUDE\fP target properties to affect
the direct dependencies of \fBapp_impl\fP\&.  To avoid this, we can revise
the property values to make their effects opt\-in:
.INDENT 0.0
.INDENT 3.5
.sp
.EX
# An app that links Foo should link Foo\(aqs plugin directly.
set_property(TARGET Foo PROPERTY INTERFACE_LINK_LIBRARIES_DIRECT
  \(dq$<$<BOOL:$<TARGET_PROPERTY:FOO_STATIC_PLUGINS>>:FooPlugin>\(dq
)

# An app does not need to link Foo directly because the plugin links it.
set_property(TARGET Foo PROPERTY INTERFACE_LINK_LIBRARIES_DIRECT_EXCLUDE
  \(dq$<$<BOOL:$<TARGET_PROPERTY:FOO_STATIC_PLUGINS>>:Foo>\(dq
)
.EE
.UNINDENT
.UNINDENT
.sp
Now, the \fBapp\fP executable can opt\-in to get \fBFoo\fP\(aqs plugin(s):
.INDENT 0.0
.INDENT 3.5
.sp
.EX
set_property(TARGET app PROPERTY FOO_STATIC_PLUGINS 1)
.EE
.UNINDENT
.UNINDENT
.sp
The final link line for \fBapp\fP will now link the libraries in the following
order:
.INDENT 0.0
.IP \(bu 2
\fBFooPlugin\fP as a direct link dependency of \fBapp\fP
(via \fBFoo\fP\(aqs usage requirements).
.IP \(bu 2
\fBapp_impl\fP as a direct link dependency of \fBapp\fP\&.
.IP \(bu 2
\fBFooExtras\fP as a dependency of \fBFooPlugin\fP\&.
.IP \(bu 2
\fBFoo\fP as a dependency of \fBapp_impl\fP, \fBFooPlugin\fP, and \fBFooExtras\fP\&.
.IP \(bu 2
\fBCore\fP as a dependency of \fBFooPlugin\fP, \fBFooExtras\fP, and \fBFoo\fP\&.
.UNINDENT
.SS INTERFACE_LINK_LIBRARIES_DIRECT_EXCLUDE
.sp
Added in version 3.24.

.sp
List of libraries that consumers of this library should \fInot\fP treat
as direct link dependencies.
.sp
This target property may be set to \fIexclude\fP items from a dependent
target\(aqs final set of direct link dependencies.  This property is
processed after the \fI\%INTERFACE_LINK_LIBRARIES_DIRECT\fP
target property of all other dependencies of the dependent target, so
exclusion from direct link dependence takes priority over inclusion.
.sp
The initial set of a dependent target\(aqs direct link dependencies is
specified by its \fI\%LINK_LIBRARIES\fP target property.  Indirect
link dependencies are specified by the transitive closure of the direct
link dependencies\(aq \fI\%INTERFACE_LINK_LIBRARIES\fP properties.
Any link dependency may specify additional direct link dependencies
using the \fI\%INTERFACE_LINK_LIBRARIES_DIRECT\fP target property.
The set of direct link dependencies is then filtered to exclude items named
by any dependency\(aqs \fBINTERFACE_LINK_LIBRARIES_DIRECT_EXCLUDE\fP target
property.
.sp
Excluding an item from a dependent target\(aqs direct link dependencies
does not mean the dependent target won\(aqt link the item.  The item
may still be linked as an indirect link dependency via the
\fI\%INTERFACE_LINK_LIBRARIES\fP property on other dependencies.
.sp
The value of \fBINTERFACE_LINK_LIBRARIES_DIRECT_EXCLUDE\fP may use
\fI\%generator expressions\fP\&.
.sp
\fBNOTE:\fP
.INDENT 0.0
.INDENT 3.5
The \fBINTERFACE_LINK_LIBRARIES_DIRECT_EXCLUDE\fP target property is intended for
advanced use cases such as injection of static plugins into a consuming
executable.  It should not be used as a substitute for organizing
normal calls to \fI\%target_link_libraries()\fP\&.
.UNINDENT
.UNINDENT
.sp
See the \fI\%INTERFACE_LINK_LIBRARIES_DIRECT\fP target property
documentation for more details and examples.
.SS INTERFACE_LINK_OPTIONS
.sp
Added in version 3.13.

.sp
List of public link options requirements for a library.
.sp
Targets may populate this property to publish the link options
required to compile against the headers for the target.  The \fI\%target_link_options()\fP
command populates this property with values given to the \fBPUBLIC\fP and
\fBINTERFACE\fP keywords.  Projects may also get and set the property directly.
.sp
When target dependencies are specified using \fI\%target_link_libraries()\fP,
CMake will read this property from all target dependencies to determine the
build properties of the consumer.
.sp
Contents of \fBINTERFACE_LINK_OPTIONS\fP may use \(dqgenerator expressions\(dq
with the syntax \fB$<...>\fP\&.  See the \fI\%cmake\-generator\-expressions(7)\fP
manual for available expressions.  See the \fI\%cmake\-buildsystem(7)\fP
\-manual for more on defining buildsystem properties.
.SS Host And Device Specific Link Options
.sp
Added in version 3.18: When a device link step is involved, which is controlled by
\fI\%CUDA_SEPARABLE_COMPILATION\fP and
\fI\%CUDA_RESOLVE_DEVICE_SYMBOLS\fP properties and policy \fI\%CMP0105\fP,
the raw options will be delivered to the host and device link steps (wrapped in
\fB\-Xcompiler\fP or equivalent for device link). Options wrapped with
\fI\%$<DEVICE_LINK:...>\fP generator expression will be used
only for the device link step. Options wrapped with \fI\%$<HOST_LINK:...>\fP
generator expression will be used only for the host link step.

.SS Option De\-duplication
.sp
The final set of options used for a target is constructed by
accumulating options from the current target and the usage requirements of
its dependencies.  The set of options is de\-duplicated to avoid repetition.
.sp
Added in version 3.12: While beneficial for individual options, the de\-duplication step can break
up option groups.  For example, \fB\-option A \-option B\fP becomes
\fB\-option A B\fP\&.  One may specify a group of options using shell\-like
quoting along with a \fBSHELL:\fP prefix.  The \fBSHELL:\fP prefix is dropped,
and the rest of the option string is parsed using the
\fI\%separate_arguments()\fP \fBUNIX_COMMAND\fP mode. For example,
\fB\(dqSHELL:\-option A\(dq \(dqSHELL:\-option B\(dq\fP becomes \fB\-option A \-option B\fP\&.

.SS Handling Compiler Driver Differences
.sp
To pass options to the linker tool, each compiler driver has its own syntax.
The \fBLINKER:\fP prefix and \fB,\fP separator can be used to specify, in a portable
way, options to pass to the linker tool. \fBLINKER:\fP is replaced by the
appropriate driver option and \fB,\fP by the appropriate driver separator.
The driver prefix and driver separator are given by the values of the
\fI\%CMAKE_<LANG>_LINKER_WRAPPER_FLAG\fP and
\fI\%CMAKE_<LANG>_LINKER_WRAPPER_FLAG_SEP\fP variables.
.sp
For example, \fB\(dqLINKER:\-z,defs\(dq\fP becomes \fB\-Xlinker \-z \-Xlinker defs\fP for
\fBClang\fP and \fB\-Wl,\-z,defs\fP for \fBGNU GCC\fP\&.
.sp
The \fBLINKER:\fP prefix can be specified as part of a \fBSHELL:\fP prefix
expression.
.sp
The \fBLINKER:\fP prefix supports, as an alternative syntax, specification of
arguments using the \fBSHELL:\fP prefix and space as separator. The previous
example then becomes \fB\(dqLINKER:SHELL:\-z defs\(dq\fP\&.
.sp
\fBNOTE:\fP
.INDENT 0.0
.INDENT 3.5
Specifying the \fBSHELL:\fP prefix anywhere other than at the beginning of the
\fBLINKER:\fP prefix is not supported.
.UNINDENT
.UNINDENT
.SS INTERFACE_POSITION_INDEPENDENT_CODE
.sp
Whether consumers need to create a position\-independent target
.sp
The \fBINTERFACE_POSITION_INDEPENDENT_CODE\fP property informs consumers of
this target whether they must set their
\fI\%POSITION_INDEPENDENT_CODE\fP property to \fBON\fP\&.  If this
property is set to \fBON\fP, then the \fI\%POSITION_INDEPENDENT_CODE\fP
property on  all consumers will be set to \fBON\fP\&. Similarly, if this
property is set to \fBOFF\fP, then the \fI\%POSITION_INDEPENDENT_CODE\fP
property on all consumers will be set to \fBOFF\fP\&.  If this property is
undefined, then consumers will determine their
\fI\%POSITION_INDEPENDENT_CODE\fP property by other means.  Consumers
must ensure that the targets that they link to have a consistent
requirement for their \fBINTERFACE_POSITION_INDEPENDENT_CODE\fP property.
.sp
Contents of \fBINTERFACE_POSITION_INDEPENDENT_CODE\fP may use
\(dqgenerator expressions\(dq with the syntax \fB$<...>\fP\&.  See the
\fI\%cmake\-generator\-expressions(7)\fP manual for available expressions.
See the \fI\%cmake\-buildsystem(7)\fP manual for more on defining buildsystem
properties.
.SS INTERFACE_PRECOMPILE_HEADERS
.sp
Added in version 3.16.

.sp
List of interface header files to precompile into consuming targets.
.sp
Targets may populate this property to publish the header files
for consuming targets to precompile.  The \fI\%target_precompile_headers()\fP
command populates this property with values given to the \fBPUBLIC\fP and
\fBINTERFACE\fP keywords.  Projects may also get and set the property directly.
See the discussion in \fI\%target_precompile_headers()\fP for guidance on
appropriate use of this property for installed or exported targets.
.sp
Contents of \fBINTERFACE_PRECOMPILE_HEADERS\fP may use \(dqgenerator expressions\(dq
with the syntax \fB$<...>\fP\&.  See the \fI\%cmake\-generator\-expressions(7)\fP
manual for available expressions.  See the \fI\%cmake\-buildsystem(7)\fP
manual for more on defining buildsystem properties.
.SS INTERFACE_SOURCES
.sp
Added in version 3.1.

.sp
List of interface sources to compile into consuming targets.
.sp
Targets may populate this property to publish the sources
for consuming targets to compile.  The \fI\%target_sources()\fP command
populates this property with values given to the \fBPUBLIC\fP and
\fBINTERFACE\fP keywords.  Projects may also get and set the property directly.
.sp
When target dependencies are specified using \fI\%target_link_libraries()\fP,
CMake will read this property from all target dependencies to determine the
sources of the consumer.
.sp
Contents of \fBINTERFACE_SOURCES\fP may use \(dqgenerator expressions\(dq
with the syntax \fB$<...>\fP\&.  See the \fI\%cmake\-generator\-expressions(7)\fP
manual for available expressions.  See the \fI\%cmake\-buildsystem(7)\fP
manual for more on defining buildsystem properties.
.SS INTERFACE_SYSTEM_INCLUDE_DIRECTORIES
.sp
List of public system include directories for a library.
.sp
Targets may populate this property to publish the include directories
which contain system headers, and therefore should not result in
compiler warnings.  Additionally, system include directories are searched
after normal include directories regardless of the order specified.
.sp
When the \fI\%target_include_directories()\fP command is given the
\fBSYSTEM\fP keyword, it populates this property with values provided after the
\fBPUBLIC\fP and \fBINTERFACE\fP keywords.
.sp
Projects may also get and set the property directly, but must be aware that
adding directories to this property does not make those directories used
during compilation.  Adding directories to this property marks directories
as system directories which otherwise would be used in a non\-system manner.
This can appear similar to duplication, so prefer the high\-level
\fI\%target_include_directories()\fP command with the \fBSYSTEM\fP keyword
and avoid setting the property directly.
.sp
When target dependencies are specified using \fI\%target_link_libraries()\fP,
CMake will read this property from all target dependencies to mark the
same include directories as containing system headers.
.sp
Contents of \fBINTERFACE_SYSTEM_INCLUDE_DIRECTORIES\fP may use \(dqgenerator
expressions\(dq with the syntax \fB$<...>\fP\&.  See the
\fI\%cmake\-generator\-expressions(7)\fP manual for available expressions.
See the \fI\%cmake\-buildsystem(7)\fP manual for more on defining
buildsystem properties.
.SS INTERPROCEDURAL_OPTIMIZATION
.sp
Enable interprocedural optimization for a target.
.sp
If set to true, enables interprocedural optimizations if they are
known \fI\%to be supported\fP by the compiler. Depending
on value of policy \fI\%CMP0069\fP, the error will be reported or ignored,
if interprocedural optimization is enabled but not supported.
.sp
This property is initialized by the
\fI\%CMAKE_INTERPROCEDURAL_OPTIMIZATION\fP variable if it is set when a
target is created.
.sp
There is also the per\-configuration \fI\%INTERPROCEDURAL_OPTIMIZATION_<CONFIG>\fP
target property, which overrides \fI\%INTERPROCEDURAL_OPTIMIZATION\fP
if it is set.
.SS See Also
.INDENT 0.0
.IP \(bu 2
The \fI\%CheckIPOSupported\fP module to check whether the compiler
supports interprocedural optimization before enabling this target property.
.UNINDENT
.SS INTERPROCEDURAL_OPTIMIZATION_<CONFIG>
.sp
Per\-configuration interprocedural optimization for a target.
.sp
This is a per\-configuration version of \fI\%INTERPROCEDURAL_OPTIMIZATION\fP\&.
If set, this property overrides the generic property for the named
configuration.
.sp
This property is initialized by the
\fI\%CMAKE_INTERPROCEDURAL_OPTIMIZATION_<CONFIG>\fP variable if it is set
when a target is created.
.SS See Also
.INDENT 0.0
.IP \(bu 2
The \fI\%CheckIPOSupported\fP module to check whether the compiler
supports interprocedural optimization before enabling this target property.
.UNINDENT
.SS ISPC_HEADER_DIRECTORY
.sp
Added in version 3.19.

.sp
Specify relative output directory for ISPC headers provided by the target.
.sp
If the target contains ISPC source files, this specifies the directory in which
the generated headers will be placed. Relative paths are treated with respect to
the value of \fI\%CMAKE_CURRENT_BINARY_DIR\fP\&. When this property is not set, the
headers will be placed a generator defined build directory. If the variable
\fI\%CMAKE_ISPC_HEADER_DIRECTORY\fP is set when a target is created
its value is used to initialize this property.
.SS ISPC_HEADER_SUFFIX
.sp
Added in version 3.19.2.

.sp
Specify output suffix to be used for ISPC generated headers provided by the target.
.sp
This property is initialized by the value of the \fI\%CMAKE_ISPC_HEADER_SUFFIX\fP
variable if it is set when a target  is created.
.sp
If the target contains ISPC source files, this specifies the header suffix to
be used for the generated headers.
.sp
The default value is \fB_ispc.h\fP\&.
.SS ISPC_INSTRUCTION_SETS
.sp
Added in version 3.19.

.sp
List of instruction set architectures to generate code for.
.sp
This property is initialized by the value of the \fI\%CMAKE_ISPC_INSTRUCTION_SETS\fP
variable if it is set when a target is created.
.sp
The \fBISPC_INSTRUCTION_SETS\fP target property must be used when generating for multiple
instruction sets so that CMake can track what object files will be generated.
.SS Examples
.INDENT 0.0
.INDENT 3.5
.sp
.EX
set_property(TARGET tgt PROPERTY ISPC_INSTRUCTION_SETS avx2\-i32x4 avx512skx\-i32x835)
.EE
.UNINDENT
.UNINDENT
.sp
Generates code for avx2 and avx512skx target architectures.
.SS JOB_POOL_COMPILE
.sp
Ninja only: Pool used for compiling.
.sp
The number of parallel compile processes could be limited by defining
pools with the global \fI\%JOB_POOLS\fP
property and then specifying here the pool name.
.sp
For instance:
.INDENT 0.0
.INDENT 3.5
.sp
.EX
set_property(TARGET myexe PROPERTY JOB_POOL_COMPILE ten_jobs)
.EE
.UNINDENT
.UNINDENT
.sp
This property is initialized by the value of
\fI\%CMAKE_JOB_POOL_COMPILE\fP\&.
.SS JOB_POOL_LINK
.sp
Ninja only: Pool used for linking.
.sp
The number of parallel link processes could be limited by defining
pools with the global \fI\%JOB_POOLS\fP
property and then specifying here the pool name.
.sp
For instance:
.INDENT 0.0
.INDENT 3.5
.sp
.EX
set_property(TARGET myexe PROPERTY JOB_POOL_LINK two_jobs)
.EE
.UNINDENT
.UNINDENT
.sp
This property is initialized by the value of \fI\%CMAKE_JOB_POOL_LINK\fP\&.
.SS JOB_POOL_PRECOMPILE_HEADER
.sp
Added in version 3.17.

.sp
Ninja only: Pool used for generating pre\-compiled headers.
.sp
The number of parallel compile processes could be limited by defining
pools with the global \fI\%JOB_POOLS\fP
property and then specifying here the pool name.
.sp
For instance:
.INDENT 0.0
.INDENT 3.5
.sp
.EX
set_property(TARGET myexe PROPERTY JOB_POOL_PRECOMPILE_HEADER two_jobs)
.EE
.UNINDENT
.UNINDENT
.sp
This property is initialized by the value of
\fI\%CMAKE_JOB_POOL_PRECOMPILE_HEADER\fP\&.
.sp
If neither \fBJOB_POOL_PRECOMPILE_HEADER\fP nor
\fI\%CMAKE_JOB_POOL_PRECOMPILE_HEADER\fP are set then
\fI\%JOB_POOL_COMPILE\fP will be used for this task.
.SS LABELS
.sp
Specify a list of text labels associated with a target.
.sp
Target label semantics are currently unspecified.
.SS <LANG>_CLANG_TIDY
.sp
Added in version 3.6.

.sp
This property is implemented only when \fB<LANG>\fP is \fBC\fP, \fBCXX\fP, \fBOBJC\fP
or \fBOBJCXX\fP\&.
.sp
Specify a \fI\%semicolon\-separated list\fP containing
a command line for the \fBclang\-tidy\fP tool.  The \fI\%Makefile Generators\fP
and the \fI\%Ninja\fP generator will run this tool along with the
compiler and report a warning if the tool reports any problems.
.sp
The specified \fBclang\-tidy\fP command line will be invoked with additional
arguments specifying the source file and, after \fB\-\-\fP, the full compiler
command line.
.sp
Changed in version 3.25: If the specified \fBclang\-tidy\fP command line includes the \fB\-p\fP option,
it will be invoked without \fB\-\-\fP and the full compiler command line.
\fBclang\-tidy\fP will look up the source file in the specified compiler
commands database.

.sp
This property is initialized by the value of
the \fI\%CMAKE_<LANG>_CLANG_TIDY\fP variable if it is set
when a target is created.
.sp
Added in version 3.27: This property supports
\fI\%generator expressions\fP\&.

.sp
Added in version 3.27: \fI\%SKIP_LINTING\fP can be set on individual source files to exclude
them from the linting tools defined by \fI\%<LANG>_CPPLINT\fP,
\fB<LANG>_CLANG_TIDY\fP, \fI\%<LANG>_CPPCHECK\fP, and
\fI\%<LANG>_INCLUDE_WHAT_YOU_USE\fP\&.  When \fI\%SKIP_LINTING\fP is
set to true on a source file, those tools will not be run on that specific
file.

.SS <LANG>_CLANG_TIDY_EXPORT_FIXES_DIR
.sp
Added in version 3.26.

.sp
This property is implemented only when \fB<LANG>\fP is \fBC\fP, \fBCXX\fP, \fBOBJC\fP
or \fBOBJCXX\fP, and only has an effect when \fI\%<LANG>_CLANG_TIDY\fP is
set.
.sp
Specify a directory for the \fBclang\-tidy\fP tool to put \fB\&.yaml\fP files
containing its suggested changes in. This can be used for automated mass
refactoring by \fBclang\-tidy\fP\&. Each object file that gets compiled will have a
corresponding \fB\&.yaml\fP file in this directory. After the build is completed,
you can run \fBclang\-apply\-replacements\fP on this directory to simultaneously
apply all suggested changes to the code base. If this property is not an
absolute directory, it is assumed to be relative to the target\(aqs binary
directory. This property should be preferred over adding an \fB\-\-export\-fixes\fP
or \fB\-\-fix\fP argument directly to the \fI\%<LANG>_CLANG_TIDY\fP property.
.sp
When this property is set, CMake takes ownership of the specified directory,
and may create, modify, or delete files and directories within the directory
at any time during configure or build time. Users should use a dedicated
directory for exporting clang\-tidy fixes to avoid having files deleted or
overwritten by CMake. Users should not create, modify, or delete files in this
directory.
.sp
This property is initialized by the value of
the \fI\%CMAKE_<LANG>_CLANG_TIDY_EXPORT_FIXES_DIR\fP variable if it is set
when a target is created.
.SS <LANG>_COMPILER_LAUNCHER
.sp
Added in version 3.4.

.sp
This property is implemented only when \fB<LANG>\fP is \fBC\fP, \fBCXX\fP,
\fBFortran\fP, \fBHIP\fP, \fBISPC\fP, \fBOBJC\fP, \fBOBJCXX\fP, or \fBCUDA\fP\&.
.sp
Specify a \fI\%semicolon\-separated list\fP containing a command line
for a compiler launching tool. The \fI\%Makefile Generators\fP and the
\fI\%Ninja\fP generator will run this tool and pass the compiler and
its arguments to the tool. Some example tools are distcc and ccache.
.sp
This property is initialized by the value of
the \fI\%CMAKE_<LANG>_COMPILER_LAUNCHER\fP variable if it is set
when a target is created.
.sp
Added in version 3.25: The property value may use
\fI\%generator expressions\fP\&.

.SS <LANG>_CPPCHECK
.sp
Added in version 3.10.

.sp
This property is supported only when \fB<LANG>\fP is \fBC\fP or \fBCXX\fP\&.
.sp
Specify a \fI\%semicolon\-separated list\fP containing a command line
for the \fBcppcheck\fP static analysis tool.  The \fI\%Makefile Generators\fP
and the \fI\%Ninja\fP generator will run \fBcppcheck\fP along with the
compiler and report any problems.  If the command\-line specifies the
exit code options to \fBcppcheck\fP then the build  will fail if the
tool returns non\-zero.
.sp
This property is initialized by the value of the
\fI\%CMAKE_<LANG>_CPPCHECK\fP variable if it is set when a target is
created.
.sp
Added in version 3.27: This property supports
\fI\%generator expressions\fP\&.

.sp
Added in version 3.27: \fI\%SKIP_LINTING\fP can be set on individual source files to exclude
them from the linting tools defined by \fI\%<LANG>_CPPLINT\fP,
\fI\%<LANG>_CLANG_TIDY\fP, \fB<LANG>_CPPCHECK\fP, and
\fI\%<LANG>_INCLUDE_WHAT_YOU_USE\fP\&.  When \fI\%SKIP_LINTING\fP is
set to true on a source file, those tools will not be run on that specific
file.

.SS <LANG>_CPPLINT
.sp
Added in version 3.8.

.sp
This property is supported only when \fB<LANG>\fP is \fBC\fP or \fBCXX\fP\&.
.sp
Specify a \fI\%semicolon\-separated list\fP containing a command line
for the \fBcpplint\fP style checker.  The \fI\%Makefile Generators\fP and the
\fI\%Ninja\fP generator will run \fBcpplint\fP along with the compiler
and report any problems.
.sp
This property is initialized by the value of the
\fI\%CMAKE_<LANG>_CPPLINT\fP variable if it is set when a target is
created.
.sp
Added in version 3.27: This property supports
\fI\%generator expressions\fP\&.

.sp
Added in version 3.27: \fI\%SKIP_LINTING\fP can be set on individual source files to exclude
them from the linting tools defined by \fB<LANG>_CPPLINT\fP,
\fI\%<LANG>_CLANG_TIDY\fP, \fI\%<LANG>_CPPCHECK\fP, and
\fI\%<LANG>_INCLUDE_WHAT_YOU_USE\fP\&.  When \fI\%SKIP_LINTING\fP is
set to true on a source file, those tools will not be run on that specific
file.

.SS <LANG>_EXTENSIONS
.sp
The variations are:
.INDENT 0.0
.IP \(bu 2
\fI\%C_EXTENSIONS\fP
.IP \(bu 2
\fI\%CXX_EXTENSIONS\fP
.IP \(bu 2
\fI\%CUDA_EXTENSIONS\fP
.IP \(bu 2
\fI\%HIP_EXTENSIONS\fP
.IP \(bu 2
\fI\%OBJC_EXTENSIONS\fP
.IP \(bu 2
\fI\%OBJCXX_EXTENSIONS\fP
.UNINDENT
.sp
These properties specify whether compiler\-specific extensions are requested.
.sp
These properties are initialized by the value of the
\fI\%CMAKE_<LANG>_EXTENSIONS\fP variable if it is set when a target is
created and otherwise by the value of
\fI\%CMAKE_<LANG>_EXTENSIONS_DEFAULT\fP (see \fI\%CMP0128\fP).
.sp
For supported CMake versions see the respective pages.
To control language standard versions see \fI\%<LANG>_STANDARD\fP\&.
.sp
See the \fI\%cmake\-compile\-features(7)\fP manual for information on
compile features and a list of supported compilers.
.SS <LANG>_ICSTAT
.sp
Added in version 4.1.

.sp
This property is supported only when \fB<LANG>\fP is \fBC\fP or \fBCXX\fP\&.
.sp
Specify a \fI\%semicolon\-separated list\fP
containing a command line for the \fBicstat\fP static analysis tool.
The \fI\%Makefile Generators\fP and the \fI\%Ninja Generators\fP will
run \fBicstat\fP along with the compiler and report any problems.
The build will fail if the \fBicstat\fP tool returns non\-zero.
.sp
This property is initialized by the value of the
\fI\%CMAKE_<LANG>_ICSTAT\fP variable if it is set when a target is
created.  It also supports
\fI\%generator expressions\fP\&.
.sp
This lint may be suppressed for individual source files by setting
the \fI\%SKIP_LINTING\fP source file property.
.SS <LANG>_INCLUDE_WHAT_YOU_USE
.sp
Added in version 3.3.

.sp
This property is implemented only when \fB<LANG>\fP is \fBC\fP or \fBCXX\fP\&.
.sp
Specify a \fI\%semicolon\-separated list\fP containing a command
line for the \fBinclude\-what\-you\-use\fP tool.  The \fI\%Makefile Generators\fP
and the \fI\%Ninja\fP generator will run this tool along with the
compiler and report a warning if the tool reports any problems.
.sp
This property is initialized by the value of
the \fI\%CMAKE_<LANG>_INCLUDE_WHAT_YOU_USE\fP variable if it is set
when a target is created.
.sp
Added in version 3.27: This property supports
\fI\%generator expressions\fP\&.

.sp
Added in version 3.27: \fI\%SKIP_LINTING\fP can be set on individual source files to exclude
them from the linting tools defined by \fI\%<LANG>_CPPLINT\fP,
\fI\%<LANG>_CLANG_TIDY\fP, \fI\%<LANG>_CPPCHECK\fP, and
\fB<LANG>_INCLUDE_WHAT_YOU_USE\fP\&.  When \fI\%SKIP_LINTING\fP is
set to true on a source file, those tools will not be run on that specific
file.

.SS <LANG>_LINKER_LAUNCHER
.sp
Added in version 3.21.

.sp
This property is implemented only when \fB<LANG>\fP is one of:
.INDENT 0.0
.IP \(bu 2
\fBC\fP
.IP \(bu 2
\fBCXX\fP
.IP \(bu 2
\fBCUDA\fP
.sp
Added in version 4.1.

.IP \(bu 2
\fBOBJC\fP
.IP \(bu 2
\fBOBJCXX\fP
.IP \(bu 2
\fBFortran\fP
.sp
Added in version 4.1.

.IP \(bu 2
\fBHIP\fP
.sp
Added in version 4.1.

.UNINDENT
.sp
Specify a \fI\%semicolon\-separated list\fP containing a
command line for a linker launching tool. The \fI\%Makefile Generators\fP and the
\fI\%Ninja\fP generator will run this tool and pass the linker and its
arguments to the tool. This is useful for tools such as static analyzers.
.sp
This property is initialized by the value of the
\fI\%CMAKE_<LANG>_LINKER_LAUNCHER\fP variable if it is set when a target is
created.
.sp
Added in version 3.27: The property value may use
\fI\%generator expressions\fP\&.

.SS <LANG>_STANDARD
.sp
The variations are:
.INDENT 0.0
.IP \(bu 2
\fI\%C_STANDARD\fP
.IP \(bu 2
\fI\%CXX_STANDARD\fP
.IP \(bu 2
\fI\%CUDA_STANDARD\fP
.IP \(bu 2
\fI\%HIP_STANDARD\fP
.IP \(bu 2
\fI\%OBJC_STANDARD\fP
.IP \(bu 2
\fI\%OBJCXX_STANDARD\fP
.UNINDENT
.sp
These properties specify language standard versions which are requested. When a
newer standard is specified than is supported by the compiler, then it will
fallback to the latest supported standard. This \(dqdecay\(dq behavior may be
controlled with the \fI\%<LANG>_STANDARD_REQUIRED\fP target property.
.sp
Note that the actual language standard used may be higher than that specified
by \fB<LANG>_STANDARD\fP, regardless of the value of
\fI\%<LANG>_STANDARD_REQUIRED\fP\&.  In particular,
\fI\%usage requirements\fP or the use of
\fI\%compile features\fP can raise the required
language standard above what \fB<LANG>_STANDARD\fP specifies.
.sp
These properties are initialized by the value of the
\fI\%CMAKE_<LANG>_STANDARD\fP variable if it is set when a target is
created.
.sp
For supported values and CMake versions see the respective pages.
To control compiler\-specific extensions see \fI\%<LANG>_EXTENSIONS\fP\&.
.sp
See the \fI\%cmake\-compile\-features(7)\fP manual for information on
compile features and a list of supported compilers.
.SS <LANG>_STANDARD_REQUIRED
.sp
The variations are:
.INDENT 0.0
.IP \(bu 2
\fI\%C_STANDARD_REQUIRED\fP
.IP \(bu 2
\fI\%CXX_STANDARD_REQUIRED\fP
.IP \(bu 2
\fI\%CUDA_STANDARD_REQUIRED\fP
.IP \(bu 2
\fI\%HIP_STANDARD_REQUIRED\fP
.IP \(bu 2
\fI\%OBJC_STANDARD_REQUIRED\fP
.IP \(bu 2
\fI\%OBJCXX_STANDARD_REQUIRED\fP
.UNINDENT
.sp
These properties specify whether the value of \fI\%<LANG>_STANDARD\fP is a
requirement.  When false or unset, the \fI\%<LANG>_STANDARD\fP target
property is treated as optional and may \(dqdecay\(dq to a previous standard if the
requested standard is not available.  When \fB<LANG>_STANDARD_REQUIRED\fP is set
to true, \fI\%<LANG>_STANDARD\fP becomes a hard requirement and a fatal
error will be issued if that requirement cannot be met.
.sp
Note that the actual language standard used may be higher than that specified
by \fI\%<LANG>_STANDARD\fP, regardless of the value of
\fB<LANG>_STANDARD_REQUIRED\fP\&.  In particular,
\fI\%usage requirements\fP or the use of
\fI\%compile features\fP can raise the required
language standard above what \fI\%<LANG>_STANDARD\fP specifies.
.sp
These properties are initialized by the value of the
\fI\%CMAKE_<LANG>_STANDARD_REQUIRED\fP variable if it is set when a target
is created.
.sp
See the \fI\%cmake\-compile\-features(7)\fP manual for information on
compile features and a list of supported compilers.
.SS <LANG>_VISIBILITY_PRESET
.sp
Value for symbol visibility compile flags
.sp
The \fB<LANG>_VISIBILITY_PRESET\fP property determines the value passed in a
visibility related compile option, such as \fB\-fvisibility=\fP for \fB<LANG>\fP\&.
This property affects compilation in sources of all types of targets.
See policy \fI\%CMP0063\fP\&.
.sp
This property is initialized by the value of the
\fI\%CMAKE_<LANG>_VISIBILITY_PRESET\fP variable if it is set when a
target is created.
.SS LIBRARY_OUTPUT_DIRECTORY
.sp
Output directory in which to build \fI\%LIBRARY\fP target files.
.sp
This property specifies the directory into which library target files
should be built.  The property value may use
\fI\%generator expressions\fP\&.
Multi\-configuration generators (\fI\%Visual Studio\fP,
\fI\%Xcode\fP, \fI\%Ninja Multi\-Config\fP) append a
per\-configuration subdirectory to the specified directory unless a generator
expression is used.
.sp
This property is initialized by the value of the
\fI\%CMAKE_LIBRARY_OUTPUT_DIRECTORY\fP variable if it is set when a target is created.
.sp
See also the \fI\%LIBRARY_OUTPUT_DIRECTORY_<CONFIG>\fP target property.
.SS LIBRARY_OUTPUT_DIRECTORY_<CONFIG>
.sp
Per\-configuration output directory for
\fI\%LIBRARY\fP target files.
.sp
This is a per\-configuration version of the
\fI\%LIBRARY_OUTPUT_DIRECTORY\fP target property, but
multi\-configuration generators (\fI\%Visual Studio Generators\fP,
\fI\%Xcode\fP) do NOT append a
per\-configuration subdirectory to the specified directory.  This
property is initialized by the value of the
\fI\%CMAKE_LIBRARY_OUTPUT_DIRECTORY_<CONFIG>\fP variable if
it is set when a target is created.
.sp
Contents of \fBLIBRARY_OUTPUT_DIRECTORY_<CONFIG>\fP may use
\fI\%generator expressions\fP\&.
.SS LIBRARY_OUTPUT_NAME
.sp
Output name for \fI\%LIBRARY\fP target files.
.sp
This property specifies the base name for library target files.  It
overrides \fI\%OUTPUT_NAME\fP and \fI\%OUTPUT_NAME_<CONFIG>\fP
properties.
.sp
See also the \fI\%LIBRARY_OUTPUT_NAME_<CONFIG>\fP target property.
.SS LIBRARY_OUTPUT_NAME_<CONFIG>
.sp
Per\-configuration output name for
\fI\%LIBRARY\fP target files.
.sp
This is the configuration\-specific version of the
\fI\%LIBRARY_OUTPUT_NAME\fP target property.
.SS SPDX_LICENSE
.sp
Added in version 4.1.

.sp
Specify the license of a target using a \X'tty: link https://spdx.dev/'\fI\%System Package Data Exchange\fP\X'tty: link' (SPDX) \X'tty: link https://spdx.github.io/spdx-spec/v3.0.1/annexes/spdx-license-expressions/'\fI\%License Expression\fP\X'tty: link'\&.
See the SPDX \X'tty: link https://spdx.org/licenses/'\fI\%License List\fP\X'tty: link' for a list of commonly used licenses and their
identifiers.
.SS LINK_DEPENDS
.sp
Additional files on which a target binary depends for linking.
.sp
Specifies a semicolon\-separated list of full\-paths to files on which
the link rule for this target depends.  The target binary will be
linked if any of the named files is newer than it.
.sp
This property is supported only by \fI\%Ninja\fP and
\fI\%Makefile Generators\fP\&.  It is
intended to specify dependencies on \(dqlinker scripts\(dq for custom Makefile link
rules.
.sp
Contents of \fBLINK_DEPENDS\fP may use \(dqgenerator expressions\(dq with
the syntax \fB$<...>\fP\&.  See the \fI\%cmake\-generator\-expressions(7)\fP
manual for available expressions.  See the \fI\%cmake\-buildsystem(7)\fP
manual for more on defining buildsystem properties.
.SS LINK_DEPENDS_NO_SHARED
.sp
Do not depend on linked shared library files.
.sp
Set this property to true to tell CMake generators not to add
file\-level dependencies on the shared library files linked by this
target.  Modification to the shared libraries will not be sufficient
to re\-link this target.  Logical target\-level dependencies will not be
affected so the linked shared libraries will still be brought up to
date before this target is built.
.sp
This property is initialized by the value of the
\fI\%CMAKE_LINK_DEPENDS_NO_SHARED\fP variable if it is set when a
target is created.
.SS LINK_DIRECTORIES
.sp
Added in version 3.13.

.sp
List of directories to use for the link step of shared library, module
and executable targets.
.sp
This property holds a \fI\%semicolon\-separated list\fP of directories
specified so far for its target.  Use the \fI\%target_link_directories()\fP
command to append more search directories.
.sp
This property is initialized by the \fI\%LINK_DIRECTORIES\fP directory
property when a target is created, and is used by the generators to set
the search directories for the linker.
.sp
Contents of \fBLINK_DIRECTORIES\fP may use \(dqgenerator expressions\(dq with the
syntax \fB$<...>\fP\&.  See the \fI\%cmake\-generator\-expressions(7)\fP manual
for available expressions.  See the \fI\%cmake\-buildsystem(7)\fP manual
for more on defining buildsystem properties.
.SS LINK_FLAGS
.sp
Additional flags to use when linking this target if it is a shared library,
module library, or an executable. Static libraries need to use
\fI\%STATIC_LIBRARY_OPTIONS\fP or \fI\%STATIC_LIBRARY_FLAGS\fP
properties.
.sp
The \fBLINK_FLAGS\fP property, managed as a string, can be used to add extra
flags to the link step of a target.  \fI\%LINK_FLAGS_<CONFIG>\fP will add
to the configuration \fB<CONFIG>\fP, for example, \fBDEBUG\fP, \fBRELEASE\fP,
\fBMINSIZEREL\fP, \fBRELWITHDEBINFO\fP, ...
.sp
\fBNOTE:\fP
.INDENT 0.0
.INDENT 3.5
This property has been superseded by \fI\%LINK_OPTIONS\fP property.
.UNINDENT
.UNINDENT
.SS LINK_FLAGS_<CONFIG>
.sp
Per\-configuration linker flags for a \fBSHARED\fP library, \fBMODULE\fP or
\fBEXECUTABLE\fP target.
.sp
This is the configuration\-specific version of \fI\%LINK_FLAGS\fP\&.
.sp
\fBNOTE:\fP
.INDENT 0.0
.INDENT 3.5
This property has been superseded by \fI\%LINK_OPTIONS\fP property.
.UNINDENT
.UNINDENT
.SS LINK_INTERFACE_LIBRARIES
.sp
List public interface libraries for a shared library or executable.
.sp
By default linking to a shared library target transitively links to
targets with which the library itself was linked.  For an executable
with exports (see the \fI\%ENABLE_EXPORTS\fP target property) no
default transitive link dependencies are used.  This property replaces the default
transitive link dependencies with an explicit list.  When the target
is linked into another target using the \fI\%target_link_libraries()\fP
command, the libraries listed (and recursively
their link interface libraries) will be provided to the other target
also.  If the list is empty then no transitive link dependencies will
be incorporated when this target is linked into another target even if
the default set is non\-empty.  This property is initialized by the
value of the \fI\%CMAKE_LINK_INTERFACE_LIBRARIES\fP variable if it is
set when a target is created.  This property is ignored for \fBSTATIC\fP
libraries.
.sp
This property is overridden by the \fI\%INTERFACE_LINK_LIBRARIES\fP
property if policy \fI\%CMP0022\fP is \fBNEW\fP\&.
.sp
This property is deprecated.  Use \fI\%INTERFACE_LINK_LIBRARIES\fP
instead.
.SS Creating Relocatable Packages
.sp
Note that it is not advisable to populate the
\fBLINK_INTERFACE_LIBRARIES\fP of a target with absolute paths to dependencies.
That would hard\-code into installed packages the library file paths
for dependencies \fBas found on the machine the package was made on\fP\&.
.sp
See the \fI\%Creating Relocatable Packages\fP section of the
\fI\%cmake\-packages(7)\fP manual for discussion of additional care
that must be taken when specifying usage requirements while creating
packages for redistribution.
.SS LINK_INTERFACE_LIBRARIES_<CONFIG>
.sp
Per\-configuration list of public interface libraries for a target.
.sp
This is the configuration\-specific version of
\fI\%LINK_INTERFACE_LIBRARIES\fP\&.  If set, this property completely
overrides the generic property for the named configuration.
.sp
This property is overridden by the \fI\%INTERFACE_LINK_LIBRARIES\fP
property if policy \fI\%CMP0022\fP is \fBNEW\fP\&.
.sp
This property is deprecated.  Use \fI\%INTERFACE_LINK_LIBRARIES\fP
instead.
.SS Creating Relocatable Packages
.sp
Note that it is not advisable to populate the
\fBLINK_INTERFACE_LIBRARIES_<CONFIG>\fP of a target with absolute paths to dependencies.
That would hard\-code into installed packages the library file paths
for dependencies \fBas found on the machine the package was made on\fP\&.
.sp
See the \fI\%Creating Relocatable Packages\fP section of the
\fI\%cmake\-packages(7)\fP manual for discussion of additional care
that must be taken when specifying usage requirements while creating
packages for redistribution.
.SS LINK_INTERFACE_MULTIPLICITY
.sp
Repetition count for \fBSTATIC\fP libraries with cyclic dependencies.
.sp
When linking to a \fBSTATIC\fP library target with cyclic dependencies the
linker may need to scan more than once through the archives in the
strongly connected component of the dependency graph.  CMake by
default constructs the link line so that the linker will scan through
the component at least twice.  This property specifies the minimum
number of scans if it is larger than the default.  CMake uses the
largest value specified by any target in a component.
.SS LINK_INTERFACE_MULTIPLICITY_<CONFIG>
.sp
Per\-configuration repetition count for cycles of \fBSTATIC\fP libraries.
.sp
This is the configuration\-specific version of
\fI\%LINK_INTERFACE_MULTIPLICITY\fP\&.  If set, this property completely
overrides the generic property for the named configuration.
.SS LINK_LIBRARIES
.sp
List of direct link dependencies.
.sp
This property specifies the list of libraries or targets which will be
used for linking.  In addition to accepting values from the
\fI\%target_link_libraries()\fP command, values may be set directly on
any target using the \fI\%set_property()\fP command.
.sp
The value of this property is used by the generators to construct the
link rule for the target.  The direct link dependencies are linked first,
followed by indirect dependencies from the transitive closure of the
direct dependencies\(aq \fI\%INTERFACE_LINK_LIBRARIES\fP properties.
See policy \fI\%CMP0022\fP\&.
.sp
Contents of \fBLINK_LIBRARIES\fP may use
\fI\%generator expressions\fP with the
syntax \fB$<...>\fP\&.  Policy \fI\%CMP0131\fP affects the behavior of the
\fI\%LINK_ONLY\fP generator expression for this property.
.sp
See the \fI\%cmake\-buildsystem(7)\fP manual for more on defining
buildsystem properties.
.sp
\fBNOTE:\fP
.INDENT 0.0
.INDENT 3.5
A call to \fI\%target_link_libraries(<target> ...)\fP may update this
property on \fB<target>\fP\&.  If \fB<target>\fP was not created in the same
directory as the call then \fI\%target_link_libraries()\fP will wrap each
entry with the form \fB::@(directory\-id);...;::@\fP, where the \fB::@\fP is
literal and the \fB(directory\-id)\fP is unspecified.
This tells the generators that the named libraries must be looked up in
the scope of the caller rather than in the scope in which the
\fB<target>\fP was created.  Valid directory ids are stripped on export
by the \fI\%install(EXPORT)\fP and \fI\%export()\fP commands.
.UNINDENT
.UNINDENT
.sp
In advanced use cases, the list of direct link dependencies specified
by this property may be updated by usage requirements from dependencies.
See the \fI\%INTERFACE_LINK_LIBRARIES_DIRECT\fP and
\fI\%INTERFACE_LINK_LIBRARIES_DIRECT_EXCLUDE\fP target properties.
.sp
See the \fI\%CMAKE_LINK_LIBRARIES_STRATEGY\fP variable and
corresponding \fI\%LINK_LIBRARIES_STRATEGY\fP target property
for details on how CMake orders direct link dependencies on linker
command lines.
.SS Handling Compiler Driver Differences
.sp
Added in version 4.0.

.sp
To pass options to the linker tool, each compiler driver has its own syntax.
The \fBLINKER:\fP prefix and \fB,\fP separator can be used to specify, in a portable
way, options to pass to the linker tool. \fBLINKER:\fP is replaced by the
appropriate driver option and \fB,\fP by the appropriate driver separator.
The driver prefix and driver separator are given by the values of the
\fI\%CMAKE_<LANG>_LINKER_WRAPPER_FLAG\fP and
\fI\%CMAKE_<LANG>_LINKER_WRAPPER_FLAG_SEP\fP variables.
.sp
For example, \fB\(dqLINKER:\-z,defs\(dq\fP becomes \fB\-Xlinker \-z \-Xlinker defs\fP for
\fBClang\fP and \fB\-Wl,\-z,defs\fP for \fBGNU GCC\fP\&.
.sp
The \fBLINKER:\fP prefix supports, as an alternative syntax, specification of
arguments using the \fBSHELL:\fP prefix and space as separator. The previous
example then becomes \fB\(dqLINKER:SHELL:\-z defs\(dq\fP\&.
.sp
\fBNOTE:\fP
.INDENT 0.0
.INDENT 3.5
Specifying the \fBSHELL:\fP prefix anywhere other than at the beginning of the
\fBLINKER:\fP prefix is not supported.
.UNINDENT
.UNINDENT
.SS LINK_LIBRARIES_ONLY_TARGETS
.sp
Added in version 3.23.

.sp
Enforce that link items that can be target names are actually existing targets.
.sp
Set this property to a true value to enable additional checks on the contents
of the \fI\%LINK_LIBRARIES\fP and \fI\%INTERFACE_LINK_LIBRARIES\fP
target properties, typically populated by \fI\%target_link_libraries()\fP\&.
Checks are also applied to libraries added to a target through the
\fI\%INTERFACE_LINK_LIBRARIES_DIRECT\fP properties of its dependencies.
CMake will verify that link items that might be target names actually name
existing targets.  An item is considered a possible target name if:
.INDENT 0.0
.IP \(bu 2
it does not contain a \fB/\fP or \fB\e\fP, and
.IP \(bu 2
it does not start in \fB\-\fP, and
.IP \(bu 2
(for historical reasons) it does not start in \fB$\fP or \fB\(ga\fP\&.
.UNINDENT
.sp
This property is initialized by the value of the
\fI\%CMAKE_LINK_LIBRARIES_ONLY_TARGETS\fP variable when a non\-imported
target is created.  The property may be explicitly enabled on an imported
target to check its link interface.
.sp
In the following example, CMake will halt with an error at configure time
because \fBmiLib\fP is not a target:
.INDENT 0.0
.INDENT 3.5
.sp
.EX
set(CMAKE_LINK_LIBRARIES_ONLY_TARGETS ON)
add_library(myLib STATIC myLib.c)
add_executable(myExe myExe.c)
target_link_libraries(myExe PRIVATE miLib) # typo for myLib
.EE
.UNINDENT
.UNINDENT
.sp
In order to link toolchain\-provided libraries by name while still
enforcing \fBLINK_LIBRARIES_ONLY_TARGETS\fP, use an
\fI\%imported\fP
\fI\%Interface Library\fP with the
\fI\%IMPORTED_LIBNAME\fP target property:
.INDENT 0.0
.INDENT 3.5
.sp
.EX
add_library(toolchain::m INTERFACE IMPORTED)
set_property(TARGET toolchain::m PROPERTY IMPORTED_LIBNAME \(dqm\(dq)
target_link_libraries(myExe PRIVATE toolchain::m)
.EE
.UNINDENT
.UNINDENT
.sp
See also policy \fI\%CMP0028\fP\&.
.sp
\fBNOTE:\fP
.INDENT 0.0
.INDENT 3.5
If \fI\%INTERFACE_LINK_LIBRARIES\fP contains generator expressions,
its actual list of link items may depend on the type and properties of
the consuming target.  In such cases CMake may not always detect names
of missing targets that only appear for specific consumers.
A future version of CMake with improved heuristics may start triggering
errors on projects accepted by previous versions of CMake.
.UNINDENT
.UNINDENT
.SS LINK_LIBRARIES_STRATEGY
.sp
Added in version 3.31.

.sp
Specify a strategy for ordering a target\(aqs direct link dependencies
on linker command lines.  This property is initialized by the value of the
\fI\%CMAKE_LINK_LIBRARIES_STRATEGY\fP variable if it is set when a
target is created.
.sp
CMake generates a target\(aqs link line using its \fI\%Target Link Properties\fP\&.
In particular, the \fI\%LINK_LIBRARIES\fP target property records the
target\(aqs direct link dependencies, typically populated by calls to
\fI\%target_link_libraries()\fP\&.  Indirect link dependencies are
propagated from those entries of \fI\%LINK_LIBRARIES\fP that name
library targets by following the transitive closure of their
\fI\%INTERFACE_LINK_LIBRARIES\fP properties.  CMake supports multiple
strategies for nominally ordering direct and indirect link dependencies,
which are then filtered for \fI\%Toolchain\-Specific Behavior\fP\&.
.sp
Consider this example for the strategies below:
.INDENT 0.0
.INDENT 3.5
.sp
.EX
add_library(A STATIC ...)
add_library(B STATIC ...)
add_library(C STATIC ...)
add_executable(main ...)
target_link_libraries(B PRIVATE A)
target_link_libraries(C PRIVATE A)
target_link_libraries(main PRIVATE A B C)
.EE
.UNINDENT
.UNINDENT
.sp
The supported strategies are:
.INDENT 0.0
.TP
.B \fBREORDER_MINIMALLY\fP
Entries of \fI\%LINK_LIBRARIES\fP always appear first and in their
original order.  Indirect link dependencies not satisfied by the
original entries may be reordered and de\-duplicated with respect to
one another, but are always appended after the original entries.
This may result in less efficient link lines, but gives projects
control of ordering among independent entries.  Such control may be
important when intermixing link flags with libraries, or when multiple
libraries provide a given symbol.
.sp
This is the default.
.sp
In the above example, this strategy computes a link line for \fBmain\fP
by starting with its original entries \fBA B C\fP, and then appends
another \fBA\fP to satisfy the dependencies of \fBB\fP and \fBC\fP on \fBA\fP\&.
The nominal order produced by this strategy is \fBA B C A\fP\&.
.sp
Note that additional filtering for \fI\%Toolchain\-Specific Behavior\fP
may de\-duplicate \fBA\fP on the actual linker invocation in the
generated build system, resulting in either \fBA B C\fP or \fBB C A\fP\&.
.TP
.B \fBREORDER_FREELY\fP
Entries of \fI\%LINK_LIBRARIES\fP may be reordered, de\-duplicated,
and intermixed with indirect link dependencies.  This may result in
more efficient link lines, but does not give projects any control of
ordering among independent entries.
.sp
In the above example, this strategy computes a link line for \fBmain\fP
by re\-ordering its original entries \fBA B C\fP to satisfy the
dependencies of \fBB\fP and \fBC\fP on \fBA\fP\&.
The nominal order produced by this strategy is \fBB C A\fP\&.
.UNINDENT
.SS Toolchain\-Specific Behavior
.sp
After one of the above strategies produces a nominal order among
direct and indirect link dependencies, the actual linker invocation
in the generated build system may de\-duplicate entries based on
platform\-specific requirements and linker capabilities.
See policy \fI\%CMP0156\fP\&.
.sp
For example, if the \fBREORDER_MINIMALLY\fP strategy produces \fBA B C A\fP,
the actual link line may de\-duplicate \fBA\fP as follows:
.INDENT 0.0
.IP \(bu 2
If \fBA\fP is a static library and the linker re\-scans automatically,
the first occurrence is kept, resulting in \fBA B C\fP\&.
See policy \fI\%CMP0179\fP
.IP \(bu 2
If \fBA\fP is a shared library on Windows, the first
occurrence is kept, resulting in \fBA B C\fP\&.
.IP \(bu 2
If \fBA\fP is a shared library on macOS or UNIX platforms, the last
occurrence is kept, resulting in \fBB C A\fP\&.
.UNINDENT
.SS LINK_LIBRARY_OVERRIDE
.sp
Added in version 3.24.

.sp
Override the library features associated with libraries from
\fI\%LINK_LIBRARY\fP generator expressions.  This can be used to resolve
incompatible library features that result from specifying different features
for the same library in different \fI\%LINK_LIBRARY\fP generator expressions.
.sp
This property supports overriding multiple libraries and features. It expects
a \fI\%semicolon\-separated list\fP, where each list item
has the following form:
.INDENT 0.0
.INDENT 3.5
.sp
.EX
feature[,link\-item]*
.EE
.UNINDENT
.UNINDENT
.sp
For each comma\-separated \fBlink\-item\fP, any existing library feature associated
with it will be ignored for the target this property is set on.  The item
will instead be associated with the specified \fBfeature\fP\&.  Each \fBlink\-item\fP
can be anything that would be accepted as part of a \fBlibrary\-list\fP in a
\fI\%LINK_LIBRARY\fP generator expression.
.INDENT 0.0
.INDENT 3.5
.sp
.EX
add_library(lib1 ...)
add_library(lib2 ...)
add_library(lib3 ...)

target_link_libraries(lib1 PUBLIC \(dq$<LINK_LIBRARY:feature1,external>\(dq)
target_link_libraries(lib2 PUBLIC \(dq$<LINK_LIBRARY:feature2,lib1>\(dq)
target_link_libraries(lib3 PRIVATE lib1 lib2)

# lib1 is associated with both feature2 and no feature. Without any override,
# this would result in a fatal error at generation time for lib3.
# Define an override to resolve the incompatible feature associations.
set_property(TARGET lib3 PROPERTY LINK_LIBRARY_OVERRIDE \(dqfeature2,lib1,external\(dq)

# lib1 and external will now be associated with feature2 instead when linking lib3
.EE
.UNINDENT
.UNINDENT
.sp
It is also possible to override any feature with the pre\-defined \fBDEFAULT\fP
library feature.  This effectively discards any feature for that link item,
for that target only (\fBlib3\fP in this example):
.INDENT 0.0
.INDENT 3.5
.sp
.EX
# When linking lib3, discard any library feature for lib1, and use feature2 for external
set_property(TARGET lib3 PROPERTY LINK_LIBRARY_OVERRIDE
  \(dqDEFAULT,lib1\(dq
  \(dqfeature2,external\(dq
)
.EE
.UNINDENT
.UNINDENT
.sp
The above example also demonstrates how to specify different feature overrides
for different link items.  See the \fI\%LINK_LIBRARY_OVERRIDE_<LIBRARY>\fP
target property for an alternative way of overriding library features for
individual libraries, which may be simpler in some cases.  If both properties
are defined and specify an override for the same link item,
\fI\%LINK_LIBRARY_OVERRIDE_<LIBRARY>\fP takes precedence over
\fBLINK_LIBRARY_OVERRIDE\fP\&.
.sp
Contents of \fBLINK_LIBRARY_OVERRIDE\fP may use
\fI\%generator expressions\fP\&.
.sp
For more information about library features, see the
\fI\%CMAKE_<LANG>_LINK_LIBRARY_USING_<FEATURE>\fP and
\fI\%CMAKE_LINK_LIBRARY_USING_<FEATURE>\fP variables.
.SS LINK_LIBRARY_OVERRIDE_<LIBRARY>
.sp
Added in version 3.24.

.sp
Override the library feature associated with \fB<LIBRARY>\fP from
\fI\%LINK_LIBRARY\fP generator expressions.  This can be used to resolve
incompatible library features that result from specifying different features
for \fB<LIBRARY>\fP in different \fI\%LINK_LIBRARY\fP generator expressions.
.sp
When set on a target, this property holds a single library feature name, which
will be applied to \fB<LIBRARY>\fP when linking that target.
.INDENT 0.0
.INDENT 3.5
.sp
.EX
add_library(lib1 ...)
add_library(lib2 ...)
add_library(lib3 ...)

target_link_libraries(lib1 PUBLIC \(dq$<LINK_LIBRARY:feature1,external>\(dq)
target_link_libraries(lib2 PUBLIC \(dq$<LINK_LIBRARY:feature2,lib1>\(dq)
target_link_libraries(lib3 PRIVATE lib1 lib2)

# lib1 is associated with both feature2 and no feature. Without any override,
# this would result in a fatal error at generation time for lib3.
# Define an override to resolve the incompatible feature associations.
set_property(TARGET lib3 PROPERTY LINK_LIBRARY_OVERRIDE_lib1 feature2)

# lib1 will now be associated with feature2 instead when linking lib3
.EE
.UNINDENT
.UNINDENT
.sp
It is also possible to override any feature with the pre\-defined \fBDEFAULT\fP
library feature.  This effectively discards any feature for that link item,
for that target only (\fBlib3\fP in this example):
.INDENT 0.0
.INDENT 3.5
.sp
.EX
# When linking lib3, discard any library feature for lib1
set_property(TARGET lib3 PROPERTY LINK_LIBRARY_OVERRIDE_lib1 DEFAULT)
.EE
.UNINDENT
.UNINDENT
.sp
See the \fI\%LINK_LIBRARY_OVERRIDE\fP target property for an alternative
way of overriding library features for multiple libraries at once.  If both
properties are defined and specify an override for the same link item,
\fBLINK_LIBRARY_OVERRIDE_<LIBRARY>\fP takes precedence over
\fI\%LINK_LIBRARY_OVERRIDE\fP\&.
.sp
Contents of \fBLINK_LIBRARY_OVERRIDE_<LIBRARY>\fP may use
\fI\%generator expressions\fP\&.
.sp
For more information about library features, see the
\fI\%CMAKE_<LANG>_LINK_LIBRARY_USING_<FEATURE>\fP and
\fI\%CMAKE_LINK_LIBRARY_USING_<FEATURE>\fP variables.
.SS LINK_OPTIONS
.sp
Added in version 3.13.

.sp
List of options to use for the link step of shared library, module
and executable targets as well as the device link step. Targets that are static
libraries need to use the \fI\%STATIC_LIBRARY_OPTIONS\fP target property.
.sp
These options are used for both normal linking and device linking
(see policy \fI\%CMP0105\fP). To control link options for normal and device
link steps, \fI\%$<HOST_LINK>\fP and \fI\%$<DEVICE_LINK>\fP generator
expressions can be used.
.sp
This property holds a \fI\%semicolon\-separated list\fP of
options specified so far for its target.  Use the \fI\%target_link_options()\fP
command to append more options.
.sp
This property is initialized by the \fI\%LINK_OPTIONS\fP directory
property when a target is created, and is used by the generators to set
the options for the compiler.
.sp
Contents of \fBLINK_OPTIONS\fP may use \(dqgenerator expressions\(dq with the
syntax \fB$<...>\fP\&.  See the \fI\%cmake\-generator\-expressions(7)\fP manual
for available expressions.  See the \fI\%cmake\-buildsystem(7)\fP manual
for more on defining buildsystem properties.
.sp
\fBNOTE:\fP
.INDENT 0.0
.INDENT 3.5
This property must be used in preference to \fI\%LINK_FLAGS\fP property.
.UNINDENT
.UNINDENT
.SS Host And Device Specific Link Options
.sp
Added in version 3.18: When a device link step is involved, which is controlled by
\fI\%CUDA_SEPARABLE_COMPILATION\fP and
\fI\%CUDA_RESOLVE_DEVICE_SYMBOLS\fP properties and policy \fI\%CMP0105\fP,
the raw options will be delivered to the host and device link steps (wrapped in
\fB\-Xcompiler\fP or equivalent for device link). Options wrapped with
\fI\%$<DEVICE_LINK:...>\fP generator expression will be used
only for the device link step. Options wrapped with \fI\%$<HOST_LINK:...>\fP
generator expression will be used only for the host link step.

.SS Option De\-duplication
.sp
The final set of options used for a target is constructed by
accumulating options from the current target and the usage requirements of
its dependencies.  The set of options is de\-duplicated to avoid repetition.
.sp
Added in version 3.12: While beneficial for individual options, the de\-duplication step can break
up option groups.  For example, \fB\-option A \-option B\fP becomes
\fB\-option A B\fP\&.  One may specify a group of options using shell\-like
quoting along with a \fBSHELL:\fP prefix.  The \fBSHELL:\fP prefix is dropped,
and the rest of the option string is parsed using the
\fI\%separate_arguments()\fP \fBUNIX_COMMAND\fP mode. For example,
\fB\(dqSHELL:\-option A\(dq \(dqSHELL:\-option B\(dq\fP becomes \fB\-option A \-option B\fP\&.

.SS Handling Compiler Driver Differences
.sp
To pass options to the linker tool, each compiler driver has its own syntax.
The \fBLINKER:\fP prefix and \fB,\fP separator can be used to specify, in a portable
way, options to pass to the linker tool. \fBLINKER:\fP is replaced by the
appropriate driver option and \fB,\fP by the appropriate driver separator.
The driver prefix and driver separator are given by the values of the
\fI\%CMAKE_<LANG>_LINKER_WRAPPER_FLAG\fP and
\fI\%CMAKE_<LANG>_LINKER_WRAPPER_FLAG_SEP\fP variables.
.sp
For example, \fB\(dqLINKER:\-z,defs\(dq\fP becomes \fB\-Xlinker \-z \-Xlinker defs\fP for
\fBClang\fP and \fB\-Wl,\-z,defs\fP for \fBGNU GCC\fP\&.
.sp
The \fBLINKER:\fP prefix can be specified as part of a \fBSHELL:\fP prefix
expression.
.sp
The \fBLINKER:\fP prefix supports, as an alternative syntax, specification of
arguments using the \fBSHELL:\fP prefix and space as separator. The previous
example then becomes \fB\(dqLINKER:SHELL:\-z defs\(dq\fP\&.
.sp
\fBNOTE:\fP
.INDENT 0.0
.INDENT 3.5
Specifying the \fBSHELL:\fP prefix anywhere other than at the beginning of the
\fBLINKER:\fP prefix is not supported.
.UNINDENT
.UNINDENT
.SS LINK_SEARCH_END_STATIC
.sp
End a link line such that static system libraries are used.
.sp
Some linkers support switches such as \fB\-Bstatic\fP and \fB\-Bdynamic\fP to
determine whether to use static or shared libraries for \fB\-lXXX\fP options.
CMake uses these options to set the link type for libraries whose full
paths are not known or (in some cases) are in implicit link
directories for the platform.  By default CMake adds an option at the
end of the library list (if necessary) to set the linker search type
back to its starting type.  This property switches the final linker
search type to \fB\-Bstatic\fP regardless of how it started.
.sp
This property is initialized by the value of the variable
\fI\%CMAKE_LINK_SEARCH_END_STATIC\fP if it is set
when a target is created.
.sp
See also \fI\%LINK_SEARCH_START_STATIC\fP\&.
.SS LINK_SEARCH_START_STATIC
.sp
Assume the linker looks for static libraries by default.
.sp
Some linkers support switches such as \fB\-Bstatic\fP and \fB\-Bdynamic\fP to
determine whether to use static or shared libraries for \fB\-lXXX\fP options.
CMake uses these options to set the link type for libraries whose full
paths are not known or (in some cases) are in implicit link
directories for the platform.  By default the linker search type is
assumed to be \fB\-Bdynamic\fP at the beginning of the library list.  This
property switches the assumption to \fB\-Bstatic\fP\&.  It is intended for use
when linking an executable statically (e.g. with the GNU \fB\-static\fP
option).
.INDENT 0.0
.TP
.B This property is initialized by the value of the variable
\fI\%CMAKE_LINK_SEARCH_START_STATIC\fP if it is set
when a target is created.
.UNINDENT
.sp
See also \fI\%LINK_SEARCH_END_STATIC\fP\&.
.SS LINK_WARNING_AS_ERROR
.sp
Added in version 4.0.

.sp
Specify whether to treat warnings on link as errors.
If enabled, adds a flag to treat warnings on link as errors.
If the \fI\%cmake \-\-link\-no\-warning\-as\-error\fP option is given
on the \fI\%cmake(1)\fP command line, this property is ignored.
.sp
This property takes a \fI\%semicolon\-separated\-list\fP of
the following values:
.INDENT 0.0
.IP \(bu 2
\fBLINKER\fP: treat the linker warnings as errors.
.IP \(bu 2
\fBDRIVER\fP: treat the compiler warnings as errors when used to drive the link
step. See the \fI\%COMPILE_WARNING_AS_ERROR\fP target property for more
information.
.UNINDENT
.sp
Moreover, for consistency with the \fI\%COMPILE_WARNING_AS_ERROR\fP target
property, a boolean value can be specified:
.INDENT 0.0
.IP \(bu 2
\fBTrue\fP value: this is equivalent to \fBLINKER\fP and \fBDRIVER\fP values.
.IP \(bu 2
\fBFalse\fP value: deactivate this feature for the target.
.UNINDENT
.sp
This property is not implemented for all linkers.  It is silently ignored
if there is no implementation for the linker being used.  The currently
implemented \fI\%compiler linker IDs\fP
are:
.INDENT 0.0
.IP \(bu 2
\fBAIX\fP
.IP \(bu 2
\fBAppleClang\fP
.IP \(bu 2
\fBGNU\fP
.IP \(bu 2
\fBGNUgold\fP
.IP \(bu 2
\fBLLD\fP
.IP \(bu 2
\fBMOLD\fP
.IP \(bu 2
\fBMSVC\fP
.IP \(bu 2
\fBSolaris\fP
.UNINDENT
.sp
This property is initialized by the value of the variable
\fI\%CMAKE_LINK_WARNING_AS_ERROR\fP if it is set when a target is
created.
.SS LINK_WHAT_YOU_USE
.sp
Added in version 3.7.

.sp
This is a boolean option that, when set to \fBTRUE\fP, adds a link\-time check
to print a list of shared libraries that are being linked but provide no symbols
used by the target.  This is intended as a lint.
.sp
The flag specified by \fI\%CMAKE_<LANG>_LINK_WHAT_YOU_USE_FLAG\fP will
be passed to the linker so that all libraries specified on the command line
will be linked into the target.  Then the command specified by
\fI\%CMAKE_LINK_WHAT_YOU_USE_CHECK\fP will run after the target is linked
to check the binary for unnecessarily\-linked shared libraries.
.sp
\fBNOTE:\fP
.INDENT 0.0
.INDENT 3.5
For now, it is only supported for \fBELF\fP platforms and is only applicable to
executable and shared or module library targets. This property will be
ignored for any other targets and configurations.
.UNINDENT
.UNINDENT
.sp
This property is initialized by the value of
the \fI\%CMAKE_LINK_WHAT_YOU_USE\fP variable if it is set
when a target is created.
.SS LINKER_LANGUAGE
.sp
Specifies language whose compiler will invoke the linker.
.sp
For executables, shared libraries, and modules, this sets the language
whose compiler is used to link the target (such as \(dqC\(dq or \(dqCXX\(dq).  A
typical value for an executable is the language of the source file
providing the program entry point (main).  If not set, the language
with the highest linker preference value is the default.  Details of
the linker preferences are considered internal, but some limited
discussion can be found under the internal
\fI\%CMAKE_<LANG>_LINKER_PREFERENCE\fP variables.
.sp
If this property is not set by the user, it will be calculated at
generate\-time by CMake.
.SS LINKER_TYPE
.sp
Added in version 3.29.

.sp
Specify which linker will be used for the link step. The property value may use
\fI\%generator expressions\fP\&.
.sp
\fBNOTE:\fP
.INDENT 0.0
.INDENT 3.5
It is assumed that the linker specified is fully compatible with the default
one the compiler would normally invoke. CMake will not do any option
translation.
.UNINDENT
.UNINDENT
.sp
Linker types are case\-sensitive and may only contain letters, numbers and
underscores. Linker types defined in all uppercase are reserved for CMake\(aqs own
built\-in types. The pre\-defined linker types are:
.INDENT 0.0
.TP
.B \fBDEFAULT\fP
This type corresponds to standard linking, essentially equivalent to the
\fI\%LINKER_TYPE\fP target property not being set at all.
.TP
.B \fBSYSTEM\fP
Use the standard linker provided by the platform or toolchain. For example,
this implies the Microsoft linker for all MSVC\-compatible compilers.
This type is supported for the following platform\-compiler combinations:
.INDENT 7.0
.IP \(bu 2
Linux: \fBGNU\fP, \fBClang\fP, \fBLLVMFlang\fP, \fBNVIDIA\fP, and \fBSwift\fP
compilers.
.IP \(bu 2
Apple platforms: \fBAppleClang\fP, \fBClang\fP, \fBGNU\fP, and \fBSwift\fP
compilers.
.IP \(bu 2
Windows: \fBMSVC\fP, \fBGNU\fP, \fBClang\fP, \fBNVIDIA\fP, and \fBSwift\fP compilers.
.UNINDENT
.TP
.B \fBLLD\fP
Use the \fBLLVM\fP linker. This type is supported for the following
platform\-compiler combinations:
.INDENT 7.0
.IP \(bu 2
Linux: \fBGNU\fP, \fBClang\fP, \fBLLVMFlang\fP, \fBNVIDIA\fP, and \fBSwift\fP
compilers.
.IP \(bu 2
Apple platforms: \fBClang\fP, \fBAppleClang\fP, and \fBSwift\fP compilers.
.IP \(bu 2
Windows: \fBGNU\fP, \fBClang\fP with MSVC\-like front\-end, \fBClang\fP with
GNU\-like front\-end, \fBMSVC\fP, \fBNVIDIA\fP with MSVC\-like front\-end,
and \fBSwift\fP\&.
.UNINDENT
.TP
.B \fBBFD\fP
Use the \fBGNU\fP linker.  This type is supported for the following
platform\-compiler combinations:
.INDENT 7.0
.IP \(bu 2
Linux: \fBGNU\fP, \fBClang\fP, \fBLLVMFlang\fP, and \fBNVIDIA\fP compilers.
.IP \(bu 2
Windows: \fBGNU\fP, \fBClang\fP with GNU\-like front\-end.
.UNINDENT
.TP
.B \fBGOLD\fP
Supported on Linux platform with \fBGNU\fP, \fBClang\fP, \fBLLVMFlang\fP,
\fBNVIDIA\fP, and \fBSwift\fP compilers.
.TP
.B \fBMOLD\fP
Use the \X'tty: link https://github.com/rui314/mold'\fI\%mold linker\fP\X'tty: link'\&. This type is
supported on the following platform\-compiler combinations:
.INDENT 7.0
.IP \(bu 2
Linux: \fBGNU\fP, \fBClang\fP, \fBLLVMFlang\fP, and \fBNVIDIA\fP compilers.
.IP \(bu 2
Apple platforms: \fBClang\fP and \fBAppleClang\fP compilers (acts as an
alias to the \X'tty: link https://github.com/bluewhalesystems/sold'\fI\%sold linker\fP\X'tty: link').
.UNINDENT
.TP
.B \fBSOLD\fP
Use the \X'tty: link https://github.com/bluewhalesystems/sold'\fI\%sold linker\fP\X'tty: link'\&. This type is only supported on Apple platforms
with \fBClang\fP and \fBAppleClang\fP compilers.
.TP
.B \fBAPPLE_CLASSIC\fP
Use the Apple linker in the classic behavior (i.e. before \fBXcode 15.0\fP).
This type is only supported on Apple platforms with \fBGNU\fP, \fBClang\fP,
\fBAppleClang\fP, and \fBSwift\fP compilers.
.TP
.B \fBMSVC\fP
Use the Microsoft linker. This type is only supported on the Windows
platform with \fBMSVC\fP, \fBClang\fP with MSVC\-like front\-end, and \fBSwift\fP
compilers.
.UNINDENT
.sp
This property is not supported on \fI\%Green Hills MULTI\fP generator.
.sp
The implementation details for the selected linker will be provided by the
\fI\%CMAKE_<LANG>_USING_LINKER_<TYPE>\fP variable. For example:
.INDENT 0.0
.INDENT 3.5
.sp
.EX
add_library(lib1 SHARED ...)
set_property(TARGET lib1 PROPERTY LINKER_TYPE LLD)
.EE
.UNINDENT
.UNINDENT
.sp
This specifies that \fBlib1\fP should use linker type \fBLLD\fP for the link step.
The command line options that will be passed to the toolchain will be provided
by the \fBCMAKE_<LANG>_USING_LINKER_LLD\fP variable.
.sp
Note that the linker would typically be set using \fI\%CMAKE_LINKER_TYPE\fP
for the whole build rather than setting the \fBLINKER_TYPE\fP property on
individual targets.
.SS LOCATION
.sp
Read\-only location of a target on disk.
.sp
For an imported target, this read\-only property returns the value of
the \fBLOCATION_<CONFIG>\fP property for an unspecified configuration
\fB<CONFIG>\fP provided by the target.
.sp
For a non\-imported target, this property is provided for compatibility
with CMake 2.4 and below.  It was meant to get the location of an
executable target\(aqs output file for use in \fI\%add_custom_command()\fP\&.  The
path may contain a build\-system\-specific portion that is replaced at
build time with the configuration getting built (such as
\fB$(ConfigurationName)\fP in VS).  In CMake 2.6 and above
\fI\%add_custom_command()\fP automatically recognizes a target name in its
\fBCOMMAND\fP and \fBDEPENDS\fP options and computes the target location.  In
CMake 2.8.4 and above \fI\%add_custom_command()\fP recognizes
\fI\%generator expressions\fP
to refer to target locations anywhere in the command.
Therefore this property is not needed for creating custom commands.
.sp
Do not set properties that affect the location of a target after
reading this property.  These include properties whose names match
\fB(RUNTIME|LIBRARY|ARCHIVE)_OUTPUT_(NAME|DIRECTORY)(_<CONFIG>)?\fP,
\fB(IMPLIB_)?(PREFIX|SUFFIX)\fP, or \(dqLINKER_LANGUAGE\(dq.  Failure to follow
this rule is not diagnosed and leaves the location of the target
undefined.
.SS LOCATION_<CONFIG>
.sp
Read\-only property providing a target location on disk.
.sp
A read\-only property that indicates where a target\(aqs main file is
located on disk for the configuration \fB<CONFIG>\fP\&.  The property is
defined only for library and executable targets.  An imported target
may provide a set of configurations different from that of the
importing project.  By default CMake looks for an exact\-match but
otherwise uses an arbitrary available configuration.  Use the
\fI\%MAP_IMPORTED_CONFIG_<CONFIG>\fP property to map imported
configurations explicitly.
.sp
Do not set properties that affect the location of a target after
reading this property.  These include properties whose names match
\fB(RUNTIME|LIBRARY|ARCHIVE)_OUTPUT_(NAME|DIRECTORY)(_<CONFIG>)?\fP,
\fB(IMPLIB_)?(PREFIX|SUFFIX)\fP, or  \fI\%LINKER_LANGUAGE\fP\&.
Failure to follow this rule is not diagnosed and leaves
the location of the target undefined.
.SS MACHO_COMPATIBILITY_VERSION
.sp
Added in version 3.17.

.sp
What compatibility version number is this target for Mach\-O binaries.
.sp
For shared libraries on Mach\-O systems (e.g. macOS, iOS)
the \fBMACHO_COMPATIBILITY_VERSION\fP property corresponds to the
\fIcompatibility version\fP and \fI\%MACHO_CURRENT_VERSION\fP corresponds to
the \fIcurrent version\fP\&.  These are both embedded in the shared library binary
and can be checked with the \fBotool \-L <binary>\fP command.
.sp
It should be noted that the \fI\%MACHO_CURRENT_VERSION\fP and
\fBMACHO_COMPATIBILITY_VERSION\fP properties do not affect the file
names or version\-related symlinks that CMake generates for the library.
The \fI\%VERSION\fP and \fI\%SOVERSION\fP target properties still
control the file and symlink names.  The \fBinstall_name\fP is also still
controlled by \fI\%SOVERSION\fP\&.
.sp
When \fI\%MACHO_CURRENT_VERSION\fP and \fBMACHO_COMPATIBILITY_VERSION\fP
are not given, \fI\%VERSION\fP and \fI\%SOVERSION\fP are used for
the version details to be embedded in the binaries respectively.
The \fI\%MACHO_CURRENT_VERSION\fP and \fBMACHO_COMPATIBILITY_VERSION\fP
properties only need to be given if the project needs to decouple the file
and symlink naming from the version details embedded in the binaries
(e.g. to match libtool conventions).
.SS MACHO_CURRENT_VERSION
.sp
Added in version 3.17.

.sp
What current version number is this target for Mach\-O binaries.
.sp
For shared libraries on Mach\-O systems (e.g. macOS, iOS)
the \fI\%MACHO_COMPATIBILITY_VERSION\fP property corresponds to the
\fIcompatibility version\fP and \fBMACHO_CURRENT_VERSION\fP corresponds to the
\fIcurrent version\fP\&.  These are both embedded in the shared library binary
and can be checked with the \fBotool \-L <binary>\fP command.
.sp
It should be noted that the \fBMACHO_CURRENT_VERSION\fP and
\fI\%MACHO_COMPATIBILITY_VERSION\fP properties do not affect the file
names or version\-related symlinks that CMake generates for the library.
The \fI\%VERSION\fP and \fI\%SOVERSION\fP target properties still
control the file and symlink names.  The \fBinstall_name\fP is also still
controlled by \fI\%SOVERSION\fP\&.
.sp
When \fBMACHO_CURRENT_VERSION\fP and \fI\%MACHO_COMPATIBILITY_VERSION\fP
are not given, \fI\%VERSION\fP and \fI\%SOVERSION\fP are used for
the version details to be embedded in the binaries respectively.
The \fBMACHO_CURRENT_VERSION\fP and \fI\%MACHO_COMPATIBILITY_VERSION\fP
properties only need to be given if the project needs to decouple the file
and symlink naming from the version details embedded in the binaries
(e.g. to match libtool conventions).
.SS MACOSX_BUNDLE
.sp
Build an executable as an Application Bundle on macOS or iOS.
.sp
When this property is set to \fBTRUE\fP the executable when built on macOS
or iOS will be created as an application bundle.  This makes it
a GUI executable that can be launched from the Finder.  See the
\fI\%MACOSX_BUNDLE_INFO_PLIST\fP target property for information about
creation of the \fBInfo.plist\fP file for the application bundle.
This property is initialized by the value of the variable
\fI\%CMAKE_MACOSX_BUNDLE\fP if it is set when a target is created.
.SS MACOSX_BUNDLE_INFO_PLIST
.sp
Specify a custom \fBInfo.plist\fP template for a macOS and iOS Application Bundle.
.sp
An executable target with \fI\%MACOSX_BUNDLE\fP enabled will be built as an
application bundle on macOS.  By default its \fBInfo.plist\fP file is created
by configuring a template called \fBMacOSXBundleInfo.plist.in\fP located in the
\fI\%CMAKE_MODULE_PATH\fP\&.  This property specifies an alternative template
file name which may be a full path.
.sp
The following target properties may be set to specify content to be
configured into the file:
.INDENT 0.0
.TP
.B \fBMACOSX_BUNDLE_BUNDLE_NAME\fP
Sets \fBCFBundleName\fP\&.
.TP
.B \fBMACOSX_BUNDLE_BUNDLE_VERSION\fP
Sets \fBCFBundleVersion\fP\&.
.TP
.B \fBMACOSX_BUNDLE_COPYRIGHT\fP
Sets \fBNSHumanReadableCopyright\fP\&.
.TP
.B \fBMACOSX_BUNDLE_GUI_IDENTIFIER\fP
Sets \fBCFBundleIdentifier\fP\&.
.TP
.B \fBMACOSX_BUNDLE_ICON_FILE\fP
Sets \fBCFBundleIconFile\fP\&.
.TP
.B \fBMACOSX_BUNDLE_INFO_STRING\fP
Sets \fBCFBundleGetInfoString\fP\&.
.TP
.B \fBMACOSX_BUNDLE_LONG_VERSION_STRING\fP
Sets \fBCFBundleLongVersionString\fP\&.
.TP
.B \fBMACOSX_BUNDLE_SHORT_VERSION_STRING\fP
Sets \fBCFBundleShortVersionString\fP\&.
.UNINDENT
.sp
CMake variables of the same name may be set to affect all targets in a
directory that do not have each specific property set.  If a custom
\fBInfo.plist\fP is specified by this property it may of course hard\-code
all the settings instead of using the target properties.
.SS MACOSX_FRAMEWORK_INFO_PLIST
.sp
Specify a custom \fBInfo.plist\fP template for a macOS and iOS Framework.
.sp
A library target with \fI\%FRAMEWORK\fP enabled will be built as a
framework on macOS.  By default its \fBInfo.plist\fP file is created by
configuring a template called \fBMacOSXFrameworkInfo.plist.in\fP located in the
\fI\%CMAKE_MODULE_PATH\fP\&.  This property specifies an alternative template
file name which may be a full path.
.sp
The following target properties may be set to specify content to be
configured into the file:
.INDENT 0.0
.TP
.B \fBMACOSX_FRAMEWORK_BUNDLE_NAME\fP
Added in version 3.31.

.sp
Sets \fBCFBundleName\fP\&.
.TP
.B \fBMACOSX_FRAMEWORK_BUNDLE_VERSION\fP
Sets \fBCFBundleVersion\fP\&.
.TP
.B \fBMACOSX_FRAMEWORK_ICON_FILE\fP
Sets \fBCFBundleIconFile\fP\&.
.TP
.B \fBMACOSX_FRAMEWORK_IDENTIFIER\fP
Sets \fBCFBundleIdentifier\fP\&.
.TP
.B \fBMACOSX_FRAMEWORK_SHORT_VERSION_STRING\fP
Sets \fBCFBundleShortVersionString\fP\&.
.UNINDENT
.sp
CMake variables of the same name may be set to affect all targets in a
directory that do not have each specific property set.  If a custom
\fBInfo.plist\fP is specified by this property it may of course hard\-code
all the settings instead of using the target properties.
.SS MACOSX_RPATH
.sp
Whether this target on macOS or iOS is located at runtime using rpaths.
.sp
When this property is set to \fBTRUE\fP, the directory portion of
the \fBinstall_name\fP field of this shared library will be \fB@rpath\fP
unless overridden by \fI\%INSTALL_NAME_DIR\fP\&.  This indicates
the shared library is to be found at runtime using runtime
paths (rpaths).
.sp
This property is initialized by the value of the variable
\fI\%CMAKE_MACOSX_RPATH\fP if it is set when a target is
created.
.sp
Runtime paths will also be embedded in binaries using this target and
can be controlled by the \fI\%INSTALL_RPATH\fP target property on
the target linking to this target.
.sp
Policy \fI\%CMP0042\fP was introduced to change the default value of
\fBMACOSX_RPATH\fP to \fBTRUE\fP\&.  This is because use of \fB@rpath\fP is a
more flexible and powerful alternative to \fB@executable_path\fP and
\fB@loader_path\fP\&.
.SS MANUALLY_ADDED_DEPENDENCIES
.sp
Added in version 3.8.

.sp
Get manually added dependencies to other top\-level targets.
.sp
This read\-only property can be used to query all dependencies that
were added for this target with the \fI\%add_dependencies()\fP
command.
.SS MAP_IMPORTED_CONFIG_<CONFIG>
.sp
Map from project configuration to
\fI\%imported target\fP\(aqs configuration.
.sp
Set this to the list of configurations of an imported target that may
be used for the current project\(aqs \fB<CONFIG>\fP configuration.  Targets
imported from another project may not provide the same set of
configuration names available in the current project.  Setting this
property tells CMake what imported configurations are suitable for use
when building the \fB<CONFIG>\fP configuration.  The first configuration in
the list found to be provided by the imported target (i.e. via
\fI\%IMPORTED_LOCATION_<CONFIG>\fP for the mapped\-to \fB<CONFIG>\fP)
is selected.  As a special case, an empty list element refers to the
configuration\-less imported target location
(i.e. \fI\%IMPORTED_LOCATION\fP).
.sp
If this property is set and no matching configurations are available,
then the imported target is considered to be not found.  This property
is ignored for non\-imported targets.
.sp
This property is initialized by the value of the
\fI\%CMAKE_MAP_IMPORTED_CONFIG_<CONFIG>\fP variable if it is set when a
target is created.
.SS Example
.sp
For example creating imported C++ library \fBfoo\fP:
.INDENT 0.0
.INDENT 3.5
.sp
.EX
add_library(foo STATIC IMPORTED)
.EE
.UNINDENT
.UNINDENT
.sp
Use \fBfoo_debug\fP path for \fBDebug\fP build type:
.INDENT 0.0
.INDENT 3.5
.sp
.EX
set_property(
  TARGET foo APPEND PROPERTY IMPORTED_CONFIGURATIONS DEBUG
  )

set_target_properties(foo PROPERTIES
  IMPORTED_LINK_INTERFACE_LANGUAGES_DEBUG \(dqCXX\(dq
  IMPORTED_LOCATION_DEBUG \(dq${foo_debug}\(dq
  )
.EE
.UNINDENT
.UNINDENT
.sp
Use \fBfoo_release\fP path for \fBRelease\fP build type:
.INDENT 0.0
.INDENT 3.5
.sp
.EX
set_property(
  TARGET foo APPEND PROPERTY IMPORTED_CONFIGURATIONS RELEASE
  )

set_target_properties(foo PROPERTIES
  IMPORTED_LINK_INTERFACE_LANGUAGES_RELEASE \(dqCXX\(dq
  IMPORTED_LOCATION_RELEASE \(dq${foo_release}\(dq
  )
.EE
.UNINDENT
.UNINDENT
.sp
Use \fBRelease\fP version of library for \fBMinSizeRel\fP and \fBRelWithDebInfo\fP
build types:
.INDENT 0.0
.INDENT 3.5
.sp
.EX
set_target_properties(foo PROPERTIES
  MAP_IMPORTED_CONFIG_MINSIZEREL Release
  MAP_IMPORTED_CONFIG_RELWITHDEBINFO Release
  )
.EE
.UNINDENT
.UNINDENT
.SS MSVC_DEBUG_INFORMATION_FORMAT
.sp
Added in version 3.25.

.sp
Select debug information format when targeting the MSVC ABI.
.sp
The allowed values are:
.INDENT 0.0
.TP
.B \fBEmbedded\fP
Compile with \fB\-Z7\fP or equivalent flag(s) to produce object files
with full symbolic debugging information.
.TP
.B \fBProgramDatabase\fP
Compile with \fB\-Zi\fP or equivalent flag(s) to produce a program
database that contains all the symbolic debugging information.
.TP
.B \fBEditAndContinue\fP
Compile with \fB\-ZI\fP or equivalent flag(s) to produce a program
database that supports the Edit and Continue feature.
.UNINDENT
.sp
The value is ignored on compilers not targeting the MSVC ABI, but an
unsupported value will be rejected as an error when using a compiler
targeting the MSVC ABI.
.sp
The value may also be the empty string (\fB\(dq\(dq\fP), in which case no debug
information format flag will be added explicitly by CMake.
.sp
Use \fI\%generator expressions\fP to
support per\-configuration specification.  For example, the code:
.INDENT 0.0
.INDENT 3.5
.sp
.EX
add_executable(foo foo.c)
set_property(TARGET foo PROPERTY
  MSVC_DEBUG_INFORMATION_FORMAT \(dq$<$<CONFIG:Debug,RelWithDebInfo>:ProgramDatabase>\(dq)
.EE
.UNINDENT
.UNINDENT
.sp
selects for the target \fBfoo\fP the program database debug information format
for the \fBDebug\fP and \fBRelWithDebInfo\fP configurations.
.sp
This property is initialized from the value of the
\fI\%CMAKE_MSVC_DEBUG_INFORMATION_FORMAT\fP variable, if it is set.
If this property is not set, CMake selects a debug information format using
the default value \fB$<$<CONFIG:Debug,RelWithDebInfo>:ProgramDatabase>\fP, if
supported by the compiler, and otherwise
\fB$<$<CONFIG:Debug,RelWithDebInfo>:Embedded>\fP\&.
.sp
\fBNOTE:\fP
.INDENT 0.0
.INDENT 3.5
This property has effect only when policy \fI\%CMP0141\fP is set to \fBNEW\fP
prior to the first \fI\%project()\fP or \fI\%enable_language()\fP command
that enables a language using a compiler targeting the MSVC ABI.
.UNINDENT
.UNINDENT
.SS MSVC_RUNTIME_CHECKS
.sp
Added in version 4.0.

.sp
Select the list of enabled runtime checks when targeting the MSVC ABI.
.sp
The allowed values are:
.INDENT 0.0
.TP
.B \fBPossibleDataLoss\fP
Compile with \fB\-RTCc\fP or equivalent flag(s) to enable possible
data loss checks.
.TP
.B \fBStackFrameErrorCheck\fP
Compile with \fB\-RTCs\fP or equivalent flag(s) to enable stack frame
error checks.
.TP
.B \fBUninitializedVariable\fP
Compile with \fB\-RTCu\fP or equivalent flag(s) to enable uninitialized
variables checks.
.UNINDENT
.sp
The value is ignored on compilers not targeting the MSVC ABI, but an
unsupported value will be rejected as an error when using a compiler
targeting the MSVC ABI.
.sp
The value may also be the empty string (\fB\(dq\(dq\fP), in which case no runtime
error check flags will be added explicitly by CMake.
.sp
Use \fI\%generator expressions\fP to
support per\-configuration specification.  For example, the code:
.INDENT 0.0
.INDENT 3.5
.sp
.EX
add_executable(foo foo.c)
set_property(TARGET foo PROPERTY
  MSVC_RUNTIME_CHECKS \(dq$<$<CONFIG:Debug,RelWithDebInfo>:PossibleDataLoss;UninitializedVariable>\(dq)
.EE
.UNINDENT
.UNINDENT
.sp
enables for the target \fBfoo\fP the possible data loss and uninitialized
variables checks for the \fBDebug\fP and \fBRelWithDebInfo\fP configurations.
.sp
This property is initialized from the value of the
\fI\%CMAKE_MSVC_RUNTIME_CHECKS\fP variable, if it is set.
If this property is not set, CMake selects runtime checks using the default
value \fB$<$<CONFIG:Debug>:StackFrameErrorCheck;UninitializedVariable>\fP,
if supported by the compiler, or an empty value otherwise.
.sp
\fBNOTE:\fP
.INDENT 0.0
.INDENT 3.5
This property has effect only when policy \fI\%CMP0184\fP is set to \fBNEW\fP
prior to the first \fI\%project()\fP or \fI\%enable_language()\fP command
that enables a language using a compiler targeting the MSVC ABI.
.UNINDENT
.UNINDENT
.SS MSVC_RUNTIME_LIBRARY
.sp
Added in version 3.15.

.sp
Select the MSVC runtime library for use by compilers targeting the MSVC ABI.
.sp
The allowed values are:
.INDENT 0.0
.TP
.B \fBMultiThreaded\fP
Compile with \fB\-MT\fP or equivalent flag(s) to use a multi\-threaded
statically\-linked runtime library.
.TP
.B \fBMultiThreadedDLL\fP
Compile with \fB\-MD\fP or equivalent flag(s) to use a multi\-threaded
dynamically\-linked runtime library.
.TP
.B \fBMultiThreadedDebug\fP
Compile with \fB\-MTd\fP or equivalent flag(s) to use a multi\-threaded
statically\-linked runtime library.
.TP
.B \fBMultiThreadedDebugDLL\fP
Compile with \fB\-MDd\fP or equivalent flag(s) to use a multi\-threaded
dynamically\-linked runtime library.
.UNINDENT
.sp
The value is ignored on compilers not targeting the MSVC ABI, but an
unsupported value will be rejected as an error when using a compiler
targeting the MSVC ABI.
.sp
The value may also be the empty string (\fB\(dq\(dq\fP) in which case no runtime
library selection flag will be added explicitly by CMake.  Note that with
\fI\%Visual Studio Generators\fP the native build system may choose to
add its own default runtime library selection flag.
.sp
Use \fI\%generator expressions\fP to
support per\-configuration specification.  For example, the code:
.INDENT 0.0
.INDENT 3.5
.sp
.EX
add_executable(foo foo.c)
set_property(TARGET foo PROPERTY
  MSVC_RUNTIME_LIBRARY \(dqMultiThreaded$<$<CONFIG:Debug>:Debug>\(dq)
.EE
.UNINDENT
.UNINDENT
.sp
selects for the target \fBfoo\fP a multi\-threaded statically\-linked runtime
library with or without debug information depending on the configuration.
.sp
The property is initialized from the value of the
\fI\%CMAKE_MSVC_RUNTIME_LIBRARY\fP variable, if it is set.
If the property is not set, then CMake uses the default value
\fBMultiThreaded$<$<CONFIG:Debug>:Debug>DLL\fP to select a MSVC runtime library.
.sp
\fBNOTE:\fP
.INDENT 0.0
.INDENT 3.5
This property has effect only when policy \fI\%CMP0091\fP is set to \fBNEW\fP
prior to the first \fI\%project()\fP or \fI\%enable_language()\fP command
that enables a language using a compiler targeting the MSVC ABI.
.UNINDENT
.UNINDENT
.SS NAME
.sp
Logical name for the target.
.sp
Read\-only logical name for the target as used by CMake.
.SS NO_SONAME
.sp
Whether to set \fBsoname\fP when linking a shared library.
.sp
Enable this boolean property if a generated \fBSHARED\fP library
should not have \fBsoname\fP set.  Default is to set \fBsoname\fP on all
shared libraries as long as the platform supports it.
Generally, use this property only for leaf private libraries or
plugins.  If you use it on normal shared libraries which other targets
link against, on some platforms a linker will insert a full path to
the library (as specified at link time) into the dynamic section of
the dependent binary.  Therefore, once installed, dynamic loader may
eventually fail to locate the library for the binary.
.SS NO_SYSTEM_FROM_IMPORTED
.sp
Do not treat include directories from the interfaces of consumed
\fI\%Imported Targets\fP as system directories.
.sp
When the consumed target\(aqs \fI\%SYSTEM\fP property is set to true, the
contents of the \fI\%INTERFACE_INCLUDE_DIRECTORIES\fP target property are
treated as system includes or, on Apple platforms, when the target is a
framework, it will be treated as system.  By default, \fI\%SYSTEM\fP is
true for imported targets and false for other target types.  If the
\fBNO_SYSTEM_FROM_IMPORTED\fP property is set to true on a \fIconsuming\fP target,
compilation of sources in that consuming target will not treat the contents of
the \fI\%INTERFACE_INCLUDE_DIRECTORIES\fP of consumed imported targets as
system includes, even if that imported target\(aqs \fI\%SYSTEM\fP property
is false.
.sp
Directories listed in the \fI\%INTERFACE_SYSTEM_INCLUDE_DIRECTORIES\fP
property of consumed targets are not affected by \fBNO_SYSTEM_FROM_IMPORTED\fP\&.
Those directories will always be treated as system include directories by
consumers.
.sp
This property is initialized by the value of the
\fI\%CMAKE_NO_SYSTEM_FROM_IMPORTED\fP variable if it is set when a target
is created.
.sp
See the \fI\%EXPORT_NO_SYSTEM\fP target property to set this behavior
on the target providing the include directories rather than the target
consuming them.
.SS OBJC_EXTENSIONS
.sp
Added in version 3.16.

.sp
Boolean specifying whether compiler specific extensions are requested.
.sp
This property specifies whether compiler specific extensions should be
used.  For some compilers, this results in adding a flag such
as \fB\-std=gnu11\fP instead of \fB\-std=c11\fP to the compile line.  This
property is \fBON\fP by default. The basic OBJC standard level is
controlled by the \fI\%OBJC_STANDARD\fP target property.
.sp
If the property is not set, and the project has set the \fI\%C_EXTENSIONS\fP,
the value of \fI\%C_EXTENSIONS\fP is set for \fBOBJC_EXTENSIONS\fP\&.
.sp
See the \fI\%cmake\-compile\-features(7)\fP manual for information on
compile features and a list of supported compilers.
.sp
This property is initialized by the value of
the \fI\%CMAKE_OBJC_EXTENSIONS\fP variable if set when a target is created
and otherwise by the value of
\fI\%CMAKE_OBJC_EXTENSIONS_DEFAULT\fP
(see \fI\%CMP0128\fP).
.SS OBJC_STANDARD
.sp
Added in version 3.16.

.sp
The OBJC standard whose features are requested to build this target.
.sp
This property specifies the OBJC standard whose features are requested
to build this target.  For some compilers, this results in adding a
flag such as \fB\-std=gnu11\fP to the compile line.
.sp
Supported values are:
.INDENT 0.0
.TP
.B \fB90\fP
Objective C89/C90
.TP
.B \fB99\fP
Objective C99
.TP
.B \fB11\fP
Objective C11
.TP
.B \fB17\fP
Added in version 3.21.

.sp
Objective C17
.TP
.B \fB23\fP
Added in version 3.21.

.sp
Objective C23
.UNINDENT
.sp
If the value requested does not result in a compile flag being added for
the compiler in use, a previous standard flag will be added instead.  This
means that using:
.INDENT 0.0
.INDENT 3.5
.sp
.EX
set_property(TARGET tgt PROPERTY OBJC_STANDARD 11)
.EE
.UNINDENT
.UNINDENT
.sp
with a compiler which does not support \fB\-std=gnu11\fP or an equivalent
flag will not result in an error or warning, but will instead add the
\fB\-std=gnu99\fP or \fB\-std=gnu90\fP flag if supported.  This \(dqdecay\(dq behavior may
be controlled with the \fI\%OBJC_STANDARD_REQUIRED\fP target property.
Additionally, the \fI\%OBJC_EXTENSIONS\fP target property may be used to
control whether compiler\-specific extensions are enabled on a per\-target basis.
.sp
If the property is not set, and the project has set the \fI\%C_STANDARD\fP,
the value of \fI\%C_STANDARD\fP is set for \fBOBJC_STANDARD\fP\&.
.sp
See the \fI\%cmake\-compile\-features(7)\fP manual for information on
compile features and a list of supported compilers.
.sp
This property is initialized by the value of
the \fI\%CMAKE_OBJC_STANDARD\fP variable if it is set when a target
is created.
.SS OBJC_STANDARD_REQUIRED
.sp
Added in version 3.16.

.sp
Boolean describing whether the value of \fI\%OBJC_STANDARD\fP is a requirement.
.sp
If this property is set to \fBON\fP, then the value of the
\fI\%OBJC_STANDARD\fP target property is treated as a requirement.  If this
property is \fBOFF\fP or unset, the \fI\%OBJC_STANDARD\fP target property is
treated as optional and may \(dqdecay\(dq to a previous standard if the requested is
not available.
.sp
If the property is not set, and the project has set the \fI\%C_STANDARD_REQUIRED\fP,
the value of \fI\%C_STANDARD_REQUIRED\fP is set for \fBOBJC_STANDARD_REQUIRED\fP\&.
.sp
See the \fI\%cmake\-compile\-features(7)\fP manual for information on
compile features and a list of supported compilers.
.sp
This property is initialized by the value of
the \fI\%CMAKE_OBJC_STANDARD_REQUIRED\fP variable if it is set when a
target is created.
.SS OBJCXX_EXTENSIONS
.sp
Added in version 3.16.

.sp
Boolean specifying whether compiler specific extensions are requested.
.sp
This property specifies whether compiler specific extensions should be
used.  For some compilers, this results in adding a flag such
as \fB\-std=gnu++11\fP instead of \fB\-std=c++11\fP to the compile line.  This
property is \fBON\fP by default. The basic ObjC++ standard level is
controlled by the \fI\%OBJCXX_STANDARD\fP target property.
.sp
See the \fI\%cmake\-compile\-features(7)\fP manual for information on
compile features and a list of supported compilers.
.sp
If the property is not set, and the project has set the \fI\%CXX_EXTENSIONS\fP,
the value of \fI\%CXX_EXTENSIONS\fP is set for \fBOBJCXX_EXTENSIONS\fP\&.
.sp
This property is initialized by the value of
the \fI\%CMAKE_OBJCXX_EXTENSIONS\fP variable if set when a target is
created and otherwise by the value of
\fI\%CMAKE_OBJCXX_EXTENSIONS_DEFAULT\fP
(see \fI\%CMP0128\fP).
.SS OBJCXX_STANDARD
.sp
Added in version 3.16.

.sp
The ObjC++ standard whose features are requested to build this target.
.sp
This property specifies the ObjC++ standard whose features are requested
to build this target.  For some compilers, this results in adding a
flag such as \fB\-std=gnu++11\fP to the compile line.
.sp
Supported values are:
.INDENT 0.0
.TP
.B \fB98\fP
Objective C++98
.TP
.B \fB11\fP
Objective C++11
.TP
.B \fB14\fP
Objective C++14
.TP
.B \fB17\fP
Objective C++17
.TP
.B \fB20\fP
Objective C++20
.TP
.B \fB23\fP
Added in version 3.20.

.sp
Objective C++23
.TP
.B \fB26\fP
Added in version 3.25.

.sp
Objective C++26. CMake 3.25 and later \fIrecognize\fP \fB26\fP as a valid value,
no version has support for any compiler.
.UNINDENT
.sp
If the value requested does not result in a compile flag being added for
the compiler in use, a previous standard flag will be added instead.  This
means that using:
.INDENT 0.0
.INDENT 3.5
.sp
.EX
set_property(TARGET tgt PROPERTY OBJCXX_STANDARD 11)
.EE
.UNINDENT
.UNINDENT
.sp
with a compiler which does not support \fB\-std=gnu++11\fP or an equivalent
flag will not result in an error or warning, but will instead add the
\fB\-std=gnu++98\fP flag if supported.  This \(dqdecay\(dq behavior may be controlled
with the \fI\%OBJCXX_STANDARD_REQUIRED\fP target property.
Additionally, the \fI\%OBJCXX_EXTENSIONS\fP target property may be used to
control whether compiler\-specific extensions are enabled on a per\-target basis.
.sp
If the property is not set, and the project has set the \fI\%CXX_STANDARD\fP,
the value of \fI\%CXX_STANDARD\fP is set for \fBOBJCXX_STANDARD\fP\&.
.sp
See the \fI\%cmake\-compile\-features(7)\fP manual for information on
compile features and a list of supported compilers.
.sp
This property is initialized by the value of
the \fI\%CMAKE_OBJCXX_STANDARD\fP variable if it is set when a target
is created.
.SS OBJCXX_STANDARD_REQUIRED
.sp
Added in version 3.16.

.sp
Boolean describing whether the value of \fI\%OBJCXX_STANDARD\fP is a requirement.
.sp
If this property is set to \fBON\fP, then the value of the
\fI\%OBJCXX_STANDARD\fP target property is treated as a requirement.  If this
property is \fBOFF\fP or unset, the \fI\%OBJCXX_STANDARD\fP target property is
treated as optional and may \(dqdecay\(dq to a previous standard if the requested is
not available.
.sp
If the property is not set, and the project has set the \fI\%CXX_STANDARD_REQUIRED\fP,
the value of \fI\%CXX_STANDARD_REQUIRED\fP is set for \fBOBJCXX_STANDARD_REQUIRED\fP\&.
.sp
See the \fI\%cmake\-compile\-features(7)\fP manual for information on
compile features and a list of supported compilers.
.sp
This property is initialized by the value of
the \fI\%CMAKE_OBJCXX_STANDARD_REQUIRED\fP variable if it is set when a
target is created.
.SS OPTIMIZE_DEPENDENCIES
.sp
Added in version 3.19.

.sp
Activates dependency optimization of static and object libraries.
.sp
When this property is set to true, some dependencies for a static or object
library may be removed at generation time if they are not necessary to build
the library, since static and object libraries don\(aqt actually link against
anything.
.sp
If a static or object library has dependency optimization enabled, it first
discards all dependencies. Then, it looks through all of the direct and
indirect dependencies that it initially had, and adds them back if they meet
any of the following criteria:
.INDENT 0.0
.IP \(bu 2
The dependency was added to the library by \fI\%add_dependencies()\fP\&.
.IP \(bu 2
The dependency was added to the library through a source file in the library
generated by a custom command that uses the dependency.
.IP \(bu 2
The dependency has any \fBPRE_BUILD\fP, \fBPRE_LINK\fP, or \fBPOST_BUILD\fP custom
commands associated with it.
.IP \(bu 2
The dependency contains any source files that were generated by a custom
command.
.IP \(bu 2
The dependency contains any languages which produce side effects that are
relevant to the library. Currently, all languages except C, C++, Objective\-C,
Objective\-C++, assembly, and CUDA are assumed to produce side effects.
However, side effects from one language are assumed not to be relevant to
another (for example, a Fortran library is assumed to not have any side
effects that are relevant for a Swift library.)
.UNINDENT
.sp
As an example, assume you have a static Fortran library which depends on a
static C library, which in turn depends on a static Fortran library. The
top\-level Fortran library has optimization enabled, but the middle C library
does not. If you build the top Fortran library, the bottom Fortran library will
also build, but not the middle C library, since the C library does not have any
side effects that are relevant for the Fortran library. However, if you build
the middle C library, the bottom Fortran library will also build, even though
it does not have any side effects that are relevant to the C library, since the
C library does not have optimization enabled.
.sp
This property is initialized by the value of the
\fI\%CMAKE_OPTIMIZE_DEPENDENCIES\fP variable when the target is created.
.SS OSX_ARCHITECTURES
.sp
Target specific architectures for macOS.
.sp
The \fBOSX_ARCHITECTURES\fP property sets the target binary architecture for
targets on macOS (\fB\-arch\fP).  This property is initialized by the value of the
variable \fI\%CMAKE_OSX_ARCHITECTURES\fP if it is set when a target is
created.  Use \fI\%OSX_ARCHITECTURES_<CONFIG>\fP to set the binary
architectures on a per\-configuration basis, where \fB<CONFIG>\fP is an
upper\-case name (e.g. \fBOSX_ARCHITECTURES_DEBUG\fP).
.SS OSX_ARCHITECTURES_<CONFIG>
.sp
Per\-configuration macOS and iOS binary architectures for a target.
.sp
This property is the configuration\-specific version of
\fI\%OSX_ARCHITECTURES\fP\&.
.SS OUTPUT_NAME
.sp
Output name for target files.
.sp
This sets the base name for output files created for an executable or
library target.  If not set, the logical target name is used by
default during generation. The value is not set by default during
configuration.
.sp
Contents of \fBOUTPUT_NAME\fP and the variants listed below may use
\fI\%generator expressions\fP\&.
.sp
See also the variants:
.INDENT 0.0
.IP \(bu 2
\fI\%OUTPUT_NAME_<CONFIG>\fP
.IP \(bu 2
\fI\%ARCHIVE_OUTPUT_NAME_<CONFIG>\fP
.IP \(bu 2
\fI\%ARCHIVE_OUTPUT_NAME\fP
.IP \(bu 2
\fI\%LIBRARY_OUTPUT_NAME_<CONFIG>\fP
.IP \(bu 2
\fI\%LIBRARY_OUTPUT_NAME\fP
.IP \(bu 2
\fI\%RUNTIME_OUTPUT_NAME_<CONFIG>\fP
.IP \(bu 2
\fI\%RUNTIME_OUTPUT_NAME\fP
.UNINDENT
.SS OUTPUT_NAME_<CONFIG>
.sp
Per\-configuration target file base name.
.sp
This is the configuration\-specific version of the \fI\%OUTPUT_NAME\fP
target property.
.SS PCH_INSTANTIATE_TEMPLATES
.sp
Added in version 3.19.

.sp
When this property is set to true, the precompiled header compiler options
will contain a flag to instantiate templates during the generation of the PCH
if supported. This can significantly improve compile times. Supported in Clang
since version 11.
.sp
This property is initialized by the value of the
\fI\%CMAKE_PCH_INSTANTIATE_TEMPLATES\fP variable if it is set when a target
is created.  If that variable is not set, the property defaults to \fBON\fP\&.
.SS PCH_WARN_INVALID
.sp
Added in version 3.18.

.sp
When this property is set to true, the precompile header compiler options
will contain a compiler flag which should warn about invalid precompiled
headers e.g. \fB\-Winvalid\-pch\fP for GNU compiler.
.sp
This property is initialized by the value of the
\fI\%CMAKE_PCH_WARN_INVALID\fP variable if it is set when a target is
created.  If that variable is not set, the property defaults to \fBON\fP\&.
.SS PDB_NAME
.sp
Output name for the MS debug symbol \fB\&.pdb\fP file generated by the
linker for an executable or shared library target.
.sp
This property specifies the base name for the debug symbols file.
If not set, the \fI\%OUTPUT_NAME\fP target property value or
logical target name is used by default.
.sp
Added in version 4.1: Contents of \fBPDB_NAME\fP may use
\fI\%generator expressions\fP\&.

.sp
\fBNOTE:\fP
.INDENT 0.0
.INDENT 3.5
This property does not apply to STATIC library targets because no linker
is invoked to produce them so they have no linker\-generated \fB\&.pdb\fP file
containing debug symbols.
.sp
The linker\-generated program database files are specified by the
\fB/pdb\fP linker flag and are not the same as compiler\-generated
program database files specified by the \fB/Fd\fP compiler flag.
Use the \fI\%COMPILE_PDB_NAME\fP property to specify the latter.
.UNINDENT
.UNINDENT
.SS PDB_NAME_<CONFIG>
.sp
Per\-configuration output name for the MS debug symbol \fB\&.pdb\fP file
generated by the linker for an executable or shared library target.
.sp
This is the configuration\-specific version of \fI\%PDB_NAME\fP\&.
.sp
Added in version 4.1: Contents of \fBPDB_NAME_<CONFIG>\fP may use
\fI\%generator expressions\fP\&.

.sp
\fBNOTE:\fP
.INDENT 0.0
.INDENT 3.5
This property does not apply to STATIC library targets because no linker
is invoked to produce them so they have no linker\-generated \fB\&.pdb\fP file
containing debug symbols.
.sp
The linker\-generated program database files are specified by the
\fB/pdb\fP linker flag and are not the same as compiler\-generated
program database files specified by the \fB/Fd\fP compiler flag.
Use the \fI\%COMPILE_PDB_NAME_<CONFIG>\fP property to specify the latter.
.UNINDENT
.UNINDENT
.SS PDB_OUTPUT_DIRECTORY
.sp
Output directory for the MS debug symbols \fB\&.pdb\fP file
generated by the linker for an executable or shared library target.
.sp
This property specifies the directory into which the MS debug symbols
will be placed by the linker.
.sp
Added in version 3.12: The property value may use
\fI\%generator expressions\fP\&.
Multi\-configuration generators append a per\-configuration
subdirectory to the specified directory unless a generator expression
is used.

.sp
This property is initialized by the value of the
\fI\%CMAKE_PDB_OUTPUT_DIRECTORY\fP variable if it is
set when a target is created.
.sp
\fBNOTE:\fP
.INDENT 0.0
.INDENT 3.5
This property does not apply to STATIC library targets because no linker
is invoked to produce them so they have no linker\-generated \fB\&.pdb\fP file
containing debug symbols.
.sp
The linker\-generated program database files are specified by the
\fB/pdb\fP linker flag and are not the same as compiler\-generated
program database files specified by the \fB/Fd\fP compiler flag.
Use the \fI\%COMPILE_PDB_OUTPUT_DIRECTORY\fP property to specify the latter.
.UNINDENT
.UNINDENT
.SS PDB_OUTPUT_DIRECTORY_<CONFIG>
.sp
Per\-configuration output directory for the MS debug symbol \fB\&.pdb\fP file
generated by the linker for an executable or shared library target.
.sp
This is a per\-configuration version of \fI\%PDB_OUTPUT_DIRECTORY\fP,
but multi\-configuration generators (\fI\%Visual Studio Generators\fP,
\fI\%Xcode\fP) do NOT append a
per\-configuration subdirectory to the specified directory.  This
property is initialized by the value of the
\fI\%CMAKE_PDB_OUTPUT_DIRECTORY_<CONFIG>\fP variable if it is
set when a target is created.
.sp
Added in version 3.12: Contents of \fBPDB_OUTPUT_DIRECTORY_<CONFIG>\fP may use
\fI\%generator expressions\fP\&.

.sp
\fBNOTE:\fP
.INDENT 0.0
.INDENT 3.5
This property does not apply to STATIC library targets because no linker
is invoked to produce them so they have no linker\-generated \fB\&.pdb\fP file
containing debug symbols.
.sp
The linker\-generated program database files are specified by the
\fB/pdb\fP linker flag and are not the same as compiler\-generated
program database files specified by the \fB/Fd\fP compiler flag.
Use the \fI\%COMPILE_PDB_OUTPUT_DIRECTORY_<CONFIG>\fP property to specify the latter.
.UNINDENT
.UNINDENT
.SS POSITION_INDEPENDENT_CODE
.sp
Whether to create a position\-independent target
.sp
The \fBPOSITION_INDEPENDENT_CODE\fP property determines whether position
independent executables or libraries will be created.  This
property is \fBTrue\fP by default for \fBSHARED\fP and \fBMODULE\fP library
targets.  For other targets, this property is initialized by the value
of the \fI\%CMAKE_POSITION_INDEPENDENT_CODE\fP variable if it is set
when the target is created, or \fBFalse\fP otherwise.
.sp
\fBNOTE:\fP
.INDENT 0.0
.INDENT 3.5
For executable targets, the link step is controlled by the \fI\%CMP0083\fP
policy and the \fI\%CheckPIESupported\fP module.
.UNINDENT
.UNINDENT
.SS PRECOMPILE_HEADERS
.sp
Added in version 3.16.

.sp
List of header files to precompile.
.sp
This property holds a \fI\%semicolon\-separated list\fP
of header files to precompile specified so far for its target.
Use the \fI\%target_precompile_headers()\fP command to append more header
files.
.sp
This property supports
\fI\%generator expressions\fP\&.
.SS PRECOMPILE_HEADERS_REUSE_FROM
.sp
Added in version 3.16.

.sp
Target from which to reuse the precompiled headers build artifact.
.sp
See the second signature of \fI\%target_precompile_headers()\fP command
for more detailed information.
.SS PREFIX
.sp
What comes before the library name.
.sp
A target property that can be set to override the prefix (such as
\fBlib\fP) on a library name.
.SS PRIVATE_HEADER
.sp
Specify private header files in a \fI\%FRAMEWORK\fP shared library target.
.sp
Shared library targets marked with the \fI\%FRAMEWORK\fP property generate
frameworks on macOS, iOS and normal shared libraries on other platforms.
This property may be set to a list of header files to be placed in the
PrivateHeaders directory inside the framework folder.  On non\-Apple
platforms these headers may be installed using the \fBPRIVATE_HEADER\fP
option to the \fI\%install(TARGETS)\fP command.
.SS PROJECT_LABEL
.sp
Change the name of a target in an IDE.
.sp
Can be used to change the name of the target in an IDE like Visual
Studio.
.SS PUBLIC_HEADER
.sp
Specify public header files in a \fI\%FRAMEWORK\fP shared library target.
.sp
Shared library targets marked with the \fI\%FRAMEWORK\fP property generate
frameworks on macOS, iOS and normal shared libraries on other platforms.
This property may be set to a list of header files to be placed in the
\fBHeaders\fP directory inside the framework folder.  On non\-Apple platforms
these headers may be installed using the \fBPUBLIC_HEADER\fP option to the
\fI\%install(TARGETS)\fP command.
.SS RESOURCE
.sp
Specify resource files in a \fI\%FRAMEWORK\fP or \fI\%BUNDLE\fP\&.
.sp
Target marked with the \fI\%FRAMEWORK\fP or \fI\%BUNDLE\fP property
generate framework or application bundle (both macOS and iOS is supported)
or normal shared libraries on other platforms.
This property may be set to a list of files to be placed in the corresponding
directory (eg. \fBResources\fP directory for macOS) inside the bundle.
On non\-Apple platforms these files may be installed using the \fBRESOURCE\fP
option to the \fI\%install(TARGETS)\fP command.
.sp
Following example of Application Bundle:
.INDENT 0.0
.INDENT 3.5
.sp
.EX
add_executable(ExecutableTarget
  addDemo.c
  resourcefile.txt
  appresourcedir/appres.txt)

target_link_libraries(ExecutableTarget heymath mul)

set(RESOURCE_FILES
  resourcefile.txt
  appresourcedir/appres.txt)

set_target_properties(ExecutableTarget PROPERTIES
  MACOSX_BUNDLE TRUE
  MACOSX_FRAMEWORK_IDENTIFIER org.cmake.ExecutableTarget
  RESOURCE \(dq${RESOURCE_FILES}\(dq)
.EE
.UNINDENT
.UNINDENT
.sp
will produce flat structure for iOS systems:
.INDENT 0.0
.INDENT 3.5
.sp
.EX
ExecutableTarget.app
  appres.txt
  ExecutableTarget
  Info.plist
  resourcefile.txt
.EE
.UNINDENT
.UNINDENT
.sp
For macOS systems it will produce following directory structure:
.INDENT 0.0
.INDENT 3.5
.sp
.EX
ExecutableTarget.app/
  Contents
    Info.plist
    MacOS
      ExecutableTarget
    Resources
      appres.txt
      resourcefile.txt
.EE
.UNINDENT
.UNINDENT
.sp
For Linux, such CMake script produce following files:
.INDENT 0.0
.INDENT 3.5
.sp
.EX
ExecutableTarget
Resources
  appres.txt
  resourcefile.txt
.EE
.UNINDENT
.UNINDENT
.SS RULE_LAUNCH_COMPILE
.sp
Specify a launcher for compile rules.
.sp
\fBNOTE:\fP
.INDENT 0.0
.INDENT 3.5
This property is intended for internal use by \fI\%ctest(1)\fP\&.  Projects
and developers should use the \fI\%<LANG>_COMPILER_LAUNCHER\fP target
properties or the associated \fI\%CMAKE_<LANG>_COMPILER_LAUNCHER\fP
variables instead.
.UNINDENT
.UNINDENT
.sp
See the \fI\%global property\fP of the same name
for details.  This overrides the global and directory property for a target.
.SS RULE_LAUNCH_CUSTOM
.sp
Specify a launcher for custom rules.
.sp
See the global property of the same name for details.  This overrides
the global and directory property for a target.
.SS RULE_LAUNCH_LINK
.sp
Specify a launcher for link rules.
.sp
\fBNOTE:\fP
.INDENT 0.0
.INDENT 3.5
This property is intended for internal use by \fI\%ctest(1)\fP\&.  Projects
and developers should use the \fI\%<LANG>_LINKER_LAUNCHER\fP target
properties or the associated \fI\%CMAKE_<LANG>_LINKER_LAUNCHER\fP
variables instead.
.UNINDENT
.UNINDENT
.sp
See the \fI\%global property\fP of the same name for
details.  This overrides the global and directory property for a target.
.SS RUNTIME_OUTPUT_DIRECTORY
.sp
Output directory in which to build \fI\%RUNTIME\fP target files.
.sp
This property specifies the directory into which runtime target files
should be built.  The property value may use
\fI\%generator expressions\fP\&.
Multi\-configuration generators (\fI\%Visual Studio\fP,
\fI\%Xcode\fP, \fI\%Ninja Multi\-Config\fP) append a
per\-configuration subdirectory to the specified directory unless a generator
expression is used.
.sp
This property is initialized by the value of the
\fI\%CMAKE_RUNTIME_OUTPUT_DIRECTORY\fP variable if it is set when a target is created.
.sp
See also the \fI\%RUNTIME_OUTPUT_DIRECTORY_<CONFIG>\fP target property.
.SS RUNTIME_OUTPUT_DIRECTORY_<CONFIG>
.sp
Per\-configuration output directory for
\fI\%RUNTIME\fP target files.
.sp
This is a per\-configuration version of the
\fI\%RUNTIME_OUTPUT_DIRECTORY\fP target property, but
multi\-configuration generators (\fI\%Visual Studio Generators\fP,
\fI\%Xcode\fP) do NOT append a
per\-configuration subdirectory to the specified directory.  This
property is initialized by the value of the
\fI\%CMAKE_RUNTIME_OUTPUT_DIRECTORY_<CONFIG>\fP variable if
it is set when a target is created.
.sp
Contents of \fBRUNTIME_OUTPUT_DIRECTORY_<CONFIG>\fP may use
\fI\%generator expressions\fP\&.
.SS RUNTIME_OUTPUT_NAME
.sp
Output name for \fI\%RUNTIME\fP target files.
.sp
This property specifies the base name for runtime target files.  It
overrides \fI\%OUTPUT_NAME\fP and \fI\%OUTPUT_NAME_<CONFIG>\fP
properties.
.sp
See also the \fI\%RUNTIME_OUTPUT_NAME_<CONFIG>\fP target property.
.SS RUNTIME_OUTPUT_NAME_<CONFIG>
.sp
Per\-configuration output name for
\fI\%RUNTIME\fP target files.
.sp
This is the configuration\-specific version of the
\fI\%RUNTIME_OUTPUT_NAME\fP target property.
.SS SKIP_BUILD_RPATH
.sp
Should rpaths be used for the build tree.
.sp
\fBSKIP_BUILD_RPATH\fP is a boolean specifying whether to skip automatic
generation of an rpath allowing the target to run from the build tree,
see also the \fI\%BUILD_RPATH\fP target property.
This property is initialized by the value of the variable
\fI\%CMAKE_SKIP_BUILD_RPATH\fP if it is set when a target is created.
.SS SOURCE_DIR
.sp
Added in version 3.4.

.sp
This read\-only property reports the value of the
\fI\%CMAKE_CURRENT_SOURCE_DIR\fP variable in the directory in which
the target was defined.
.SS SOURCES
.sp
This specifies the list of paths to source files for the target.
The following commands all set or add to the \fBSOURCES\fP target property
and are the usual way to manipulate it:
.INDENT 0.0
.IP \(bu 2
\fI\%add_executable()\fP
.IP \(bu 2
\fI\%add_library()\fP
.IP \(bu 2
\fI\%add_custom_target()\fP
.IP \(bu 2
\fI\%target_sources()\fP
.UNINDENT
.sp
Contents of \fBSOURCES\fP may use
\fI\%generator expressions\fP\&.
If a path starts with a generator expression, it is expected to
evaluate to an absolute path. Not doing so is considered undefined behavior.
.sp
Paths that are for files generated by the build will be treated
as relative to the build directory of the target, if the path is not
already specified as an absolute path.  Note that whether a file is seen as
generated may be affected by policies \fI\%CMP0118\fP and \fI\%CMP0163\fP\&.
.sp
If a path does not start with a generator expression, is not an
absolute path and is not a generated file, it will be treated as relative to
the location selected by the first of the following that matches:
.INDENT 0.0
.IP \(bu 2
If a file by the specified path exists relative to the target\(aqs source
directory, use that file.
.IP \(bu 2
If policy \fI\%CMP0115\fP is not set to \fBNEW\fP, try appending each
known source file extension to the path and check if that exists
relative to the target\(aqs source directory.
.IP \(bu 2
Repeat the above two steps, this time relative to the target\(aqs binary
directory instead.
.UNINDENT
.sp
Note that the above decisions are made at generation time, not build time.
.sp
See the \fI\%cmake\-buildsystem(7)\fP manual for more on defining
buildsystem properties.
.SS SOVERSION
.sp
ABI version number of a shared library target.
.sp
For shared libraries \fI\%VERSION\fP and \fBSOVERSION\fP can be used to
specify the build version and ABI version respectively.  When building or
installing appropriate symlinks are created if the platform supports
symlinks and the linker supports so\-names.  If only one of both is
specified the missing is assumed to have the same version number.
\fBSOVERSION\fP is ignored if \fI\%NO_SONAME\fP property is set.
.sp
A common convention is to specify both \fBVERSION\fP and \fBSOVERSION\fP
such that \fBSOVERSION\fP matches the first component of \fBVERSION\fP:
.INDENT 0.0
.INDENT 3.5
.sp
.EX
set_target_properties(mylib PROPERTIES VERSION 1.2.3 SOVERSION 1)
.EE
.UNINDENT
.UNINDENT
.sp
The idea is that breaking changes to the ABI increment both the
\fBSOVERSION\fP and the major \fBVERSION\fP number.
.SS Windows Versions
.sp
For shared libraries and executables on Windows the \fI\%VERSION\fP
attribute is parsed to extract a \fB<major>.<minor>\fP version number.
These numbers are used as the image version of the binary.
.SS Mach\-O Versions
.sp
For shared libraries and executables on Mach\-O systems (e.g. macOS, iOS),
the \fBSOVERSION\fP property corresponds to the \fIcompatibility version\fP and
\fI\%VERSION\fP corresponds to the \fIcurrent version\fP (unless Mach\-O
specific overrides are provided, as discussed below).
See the \fI\%FRAMEWORK\fP target property for an example.
.sp
For shared libraries, the \fI\%MACHO_COMPATIBILITY_VERSION\fP and
\fI\%MACHO_CURRENT_VERSION\fP properties can be used to
override the \fIcompatibility version\fP and \fIcurrent version\fP respectively.
Note that \fBSOVERSION\fP will still be used to form the \fBinstall_name\fP
and both \fBSOVERSION\fP and \fI\%VERSION\fP may also affect the file
and symlink names.
.sp
Versions of Mach\-O binaries may be checked with the \fBotool \-L <binary>\fP
command.
.SS STATIC_LIBRARY_FLAGS
.sp
Archiver (or MSVC librarian) flags for a static library target.
Targets that are shared libraries, modules, or executables need to use
the \fI\%LINK_OPTIONS\fP or \fI\%LINK_FLAGS\fP target properties.
.sp
The \fBSTATIC_LIBRARY_FLAGS\fP property, managed as a string, can be used to add
extra flags to the link step of a static library target.
\fI\%STATIC_LIBRARY_FLAGS_<CONFIG>\fP will add to the configuration
\fB<CONFIG>\fP, for example, \fBDEBUG\fP, \fBRELEASE\fP, \fBMINSIZEREL\fP,
\fBRELWITHDEBINFO\fP, ...
.sp
\fBNOTE:\fP
.INDENT 0.0
.INDENT 3.5
This property has been superseded by \fI\%STATIC_LIBRARY_OPTIONS\fP
property.
.UNINDENT
.UNINDENT
.SS STATIC_LIBRARY_FLAGS_<CONFIG>
.sp
Per\-configuration archiver (or MSVC librarian) flags for a static library
target.
.sp
This is the configuration\-specific version of \fI\%STATIC_LIBRARY_FLAGS\fP\&.
.sp
\fBNOTE:\fP
.INDENT 0.0
.INDENT 3.5
This property has been superseded by \fI\%STATIC_LIBRARY_OPTIONS\fP
property.
.UNINDENT
.UNINDENT
.SS STATIC_LIBRARY_OPTIONS
.sp
Added in version 3.13.

.sp
Archiver (or MSVC librarian) flags for a static library target.
Targets that are shared libraries, modules, or executables need to use
the \fI\%LINK_OPTIONS\fP target property.
.sp
This property holds a \fI\%semicolon\-separated list\fP of options
specified so far for its target.  Use \fI\%set_target_properties()\fP or
\fI\%set_property()\fP commands to set its content.
.sp
Contents of \fBSTATIC_LIBRARY_OPTIONS\fP may use \(dqgenerator expressions\(dq with the
syntax \fB$<...>\fP\&.  See the \fI\%cmake\-generator\-expressions(7)\fP manual
for available expressions.  See the \fI\%cmake\-buildsystem(7)\fP manual
for more on defining buildsystem properties.
.sp
\fBNOTE:\fP
.INDENT 0.0
.INDENT 3.5
This property must be used in preference to \fI\%STATIC_LIBRARY_FLAGS\fP
property.
.UNINDENT
.UNINDENT
.SS Option De\-duplication
.sp
The final set of options used for a target is constructed by
accumulating options from the current target and the usage requirements of
its dependencies.  The set of options is de\-duplicated to avoid repetition.
.sp
Added in version 3.12: While beneficial for individual options, the de\-duplication step can break
up option groups.  For example, \fB\-option A \-option B\fP becomes
\fB\-option A B\fP\&.  One may specify a group of options using shell\-like
quoting along with a \fBSHELL:\fP prefix.  The \fBSHELL:\fP prefix is dropped,
and the rest of the option string is parsed using the
\fI\%separate_arguments()\fP \fBUNIX_COMMAND\fP mode. For example,
\fB\(dqSHELL:\-option A\(dq \(dqSHELL:\-option B\(dq\fP becomes \fB\-option A \-option B\fP\&.

.SS Handling Archiver Driver Differences
.sp
Added in version 4.0.

.sp
To pass options to the archiver tool, each compiler driver has its own syntax.
The \fBARCHIVER:\fP prefix and \fB,\fP separator can be used to specify, in a portable
way, options to pass to the archiver tool. \fBARCHIVER:\fP is replaced by the
appropriate driver option and \fB,\fP by the appropriate driver separator.
The driver prefix and driver separator are given by the values of the
\fI\%CMAKE_<LANG>_ARCHIVER_WRAPPER_FLAG\fP and
\fI\%CMAKE_<LANG>_ARCHIVER_WRAPPER_FLAG_SEP\fP variables.
.sp
The \fBARCHIVER:\fP prefix can be specified as part of a \fBSHELL:\fP prefix
expression.
.sp
The \fBARCHIVER:\fP prefix supports, as an alternative syntax, specification of
arguments using the \fBSHELL:\fP prefix and space as separator.
.sp
\fBNOTE:\fP
.INDENT 0.0
.INDENT 3.5
Specifying the \fBSHELL:\fP prefix anywhere other than at the beginning of the
\fBARCHIVER:\fP prefix is not supported.
.UNINDENT
.UNINDENT
.SS SUFFIX
.sp
What comes after the target name.
.sp
A target property that can be set to override the suffix (such as
\fB\&.so\fP or \fB\&.exe\fP) on the name of a library, module or executable.
.SS Swift_COMPILATION_MODE
.sp
Added in version 3.29.

.sp
Specify how Swift compiles a target.
.sp
The allowed values are:
.INDENT 0.0
.TP
.B \fBincremental\fP
Compiles each Swift source in the module separately, resulting in better
parallelism in the build. The compiler emits additional information into
the build directory improving rebuild performance when small changes are made
to the source between rebuilds. This is the best option to use while
iterating on changes in a project.
.TP
.B \fBwholemodule\fP
Whole\-module optimizations are slowest to compile, but results in the most
optimized library. The entire context is loaded into once instance of the
compiler, so there is no parallelism across source files in the module.
.TP
.B \fBsinglefile\fP
Compiles each source in a Swift modules separately, resulting in better
parallelism. Unlike the \fBincremental\fP build mode, no additional information
is emitted by the compiler during the build, so rebuilding after making small
changes to the source file will not run faster. This option should be used
sparingly, preferring \fBincremental\fP builds, unless working around a compiler
bug.
.UNINDENT
.sp
Use \fI\%generator expressions\fP to support
per\-configuration specification. For example, the code:
.INDENT 0.0
.INDENT 3.5
.sp
.EX
add_library(foo foo.swift)
set_property(TARGET foo PROPERTY
  Swift_COMPILATION_MODE \(dq$<IF:$<CONFIG:Release>,wholemodule,incremental>\(dq)
.EE
.UNINDENT
.UNINDENT
.sp
sets the Swift compilation mode to wholemodule mode in the release configuration
and sets the property to incremental mode in other configurations.
.sp
The property is initialized from the value of the
\fI\%CMAKE_Swift_COMPILATION_MODE\fP variable, if it is set. If the property
is not set or is empty, then CMake uses the default value \fBincremental\fP to
specify the swift compilation mode.
.sp
\fBNOTE:\fP
.INDENT 0.0
.INDENT 3.5
This property only has effect when policy \fI\%CMP0157\fP is set to \fBNEW\fP
prior to the first \fI\%project()\fP or \fI\%enable_language()\fP command
that enables the Swift language.
.UNINDENT
.UNINDENT
.SS Swift_DEPENDENCIES_FILE
.sp
Added in version 3.15.

.sp
This property sets the path for the Swift dependency file (swiftdep) for the
target.  If one is not specified, it will default to \fB<TARGET>.swiftdeps\fP\&.
.SS Swift_LANGUAGE_VERSION
.sp
Added in version 3.16.

.sp
This property sets the language version for the Swift sources in the target.  If
one is not specified, it will default to
\fI\%CMAKE_Swift_LANGUAGE_VERSION\fP if specified, otherwise it is the
latest version supported by the compiler.
.SS Swift_MODULE_DIRECTORY
.sp
Added in version 3.15.

.sp
Specify output directory for Swift modules provided by the target.
.sp
If the target contains Swift source files, this specifies the directory in which
the modules will be placed.  When this property is not set, the modules will be
placed in the build directory corresponding to the target\(aqs source directory.
If the variable \fI\%CMAKE_Swift_MODULE_DIRECTORY\fP is set when a target is
created its value is used to initialize this property.
.sp
Added in version 4.0: The property value may use
\fI\%generator expressions\fP\&.
Multi\-configuration generators (\fI\%Ninja Multi\-Config\fP) append a
per\-configuration subdirectory to the specified directory unless a generator
expression is used.

.sp
\fBWARNING:\fP
.INDENT 0.0
.INDENT 3.5
The \fI\%Xcode\fP generator ignores this property.
.UNINDENT
.UNINDENT
.SS Swift_MODULE_NAME
.sp
Added in version 3.15.

.sp
This property specifies the name of the Swift module.  It is defaulted to the
name of the target.
.SS SYSTEM
.sp
Added in version 3.25.

.sp
Specifies that a target is a system target.  This has the following
effects:
.INDENT 0.0
.IP \(bu 2
Entries of \fI\%INTERFACE_INCLUDE_DIRECTORIES\fP are treated as
system include directories when compiling consumers.
Entries of \fI\%INTERFACE_SYSTEM_INCLUDE_DIRECTORIES\fP are not
affected, and will always be treated as system include directories.
.IP \(bu 2
On Apple platforms, If the \fI\%FRAMEWORK\fP target property is true,
the frameworks directory is treated as system.
.UNINDENT
.sp
For imported targets, this property defaults to true, which means
that their \fI\%INTERFACE_INCLUDE_DIRECTORIES\fP and, if the
\fI\%FRAMEWORK\fP target property is true, frameworks directory are
treated as system directories by default.  If their \fBSYSTEM\fP property is
false, then their \fI\%INTERFACE_INCLUDE_DIRECTORIES\fP as well as
frameworks will not be treated as system.  Use the \fI\%EXPORT_NO_SYSTEM\fP
property to change how a target\(aqs \fBSYSTEM\fP property is set when it is
installed.
.sp
For non\-imported targets, this target property is initialized from
the \fI\%SYSTEM\fP directory property when the target is created.
.SS TEST_LAUNCHER
.sp
Added in version 3.29.

.sp
Use the given launcher to run executables.
This command will be added as a prefix to \fI\%add_test()\fP commands
for build target system executables and is meant to be run on the host
machine.
.sp
It effectively acts as a run script for tests in a similar way
to how \fI\%CMAKE_<LANG>_COMPILER_LAUNCHER\fP works for compilation.
.sp
If this property contains a \fI\%semicolon\-separated list\fP, then the first value is the command and remaining values are its
arguments.
.sp
Contents of \fBTEST_LAUNCHER\fP may use
\fI\%generator expressions\fP\&.
.sp
This property is initialized by the value of the
\fI\%CMAKE_TEST_LAUNCHER\fP variable if it is set when a target
is created.
.SS TRANSITIVE_COMPILE_PROPERTIES
.sp
Added in version 3.30.

.sp
Properties that the \fI\%TARGET_PROPERTY\fP generator expression, on the
target and its dependents, evaluates as the union of values collected from
the transitive closure of link dependencies, excluding entries guarded by
\fI\%LINK_ONLY\fP\&.
.sp
The value is a \fI\%semicolon\-separated list\fP
of \fI\%custom transitive property\fP names.
Any leading \fBINTERFACE_\fP prefix is ignored, e.g., \fBINTERFACE_PROP\fP is
treated as just \fBPROP\fP\&.
.sp
See documentation of the \fI\%TARGET_PROPERTY\fP generator expression
for details of custom transitive property evaluation.  See also the
\fI\%TRANSITIVE_LINK_PROPERTIES\fP target property, which includes
entries guarded by \fI\%LINK_ONLY\fP\&.
.SS TRANSITIVE_LINK_PROPERTIES
.sp
Added in version 3.30.

.sp
Properties that the \fI\%TARGET_PROPERTY\fP generator expression, on the
target and its dependents, evaluates as the union of values collected from
the transitive closure of link dependencies, including entries guarded by
\fI\%LINK_ONLY\fP\&.
.sp
The value is a \fI\%semicolon\-separated list\fP
of \fI\%custom transitive property\fP names.
Any leading \fBINTERFACE_\fP prefix is ignored, e.g., \fBINTERFACE_PROP\fP is
treated as just \fBPROP\fP\&.
.sp
See documentation of the \fI\%TARGET_PROPERTY\fP generator expression
for details of custom transitive property evaluation.  See also the
\fI\%TRANSITIVE_COMPILE_PROPERTIES\fP target property, which excludes
entries guarded by \fI\%LINK_ONLY\fP\&..
.SS TYPE
.sp
The type of the target.
.sp
This read\-only property can be used to test the type of the given
target.  It will be one of \fBSTATIC_LIBRARY\fP, \fBMODULE_LIBRARY\fP,
\fBSHARED_LIBRARY\fP, \fBOBJECT_LIBRARY\fP, \fBINTERFACE_LIBRARY\fP, \fBEXECUTABLE\fP
or one of the internal target types.
.SS UNITY_BUILD
.sp
Added in version 3.16.

.sp
When this property is set to true, the target source files will be combined
into batches for faster compilation.  This is done by creating a (set of)
unity sources which \fB#include\fP the original sources, then compiling these
unity sources instead of the originals.  This is known as a \fIUnity\fP or \fIJumbo\fP
build.
.sp
CMake provides different algorithms for selecting which sources are grouped
together into a \fIbucket\fP\&. Algorithm selection is decided by the
\fI\%UNITY_BUILD_MODE\fP target property, which has the following acceptable
values:
.INDENT 0.0
.IP \(bu 2
\fBBATCH\fP
When in this mode CMake determines which files are grouped together.
The \fI\%UNITY_BUILD_BATCH_SIZE\fP property controls the upper limit on
how many sources can be combined per unity source file.
.IP \(bu 2
\fBGROUP\fP
When in this mode each target explicitly specifies how to group
source files. Each source file that has the same
\fI\%UNITY_GROUP\fP value will be grouped together. Any sources
that don\(aqt have this property will be compiled individually. The
\fI\%UNITY_BUILD_BATCH_SIZE\fP property is ignored when using
this mode.
.UNINDENT
.sp
If no explicit \fI\%UNITY_BUILD_MODE\fP has been specified, CMake will
default to \fBBATCH\fP\&.
.sp
Unity builds are supported for the following languages:
.INDENT 0.0
.TP
.B \fBC\fP
Added in version 3.16.

.TP
.B \fBCXX\fP
Added in version 3.16.

.TP
.B \fBCUDA\fP
Added in version 3.31.

.TP
.B \fBOBJC\fP
Added in version 3.29.

.TP
.B \fBOBJCXX\fP
Added in version 3.29.

.UNINDENT
.sp
For targets that mix source files from more than one language, CMake
separates the languages such that each generated unity source file only
contains sources for a single language.
.sp
This property is initialized by the value of the \fI\%CMAKE_UNITY_BUILD\fP
variable when a target is created.
.sp
\fBNOTE:\fP
.INDENT 0.0
.INDENT 3.5
Projects should not directly set the \fBUNITY_BUILD\fP property or its
associated \fI\%CMAKE_UNITY_BUILD\fP variable to true.  Depending
on the capabilities of the build machine and compiler used, it might or
might not be appropriate to enable unity builds.  Therefore, this feature
should be under developer control, which would normally be through the
developer choosing whether or not to set the \fI\%CMAKE_UNITY_BUILD\fP
variable on the \fI\%cmake(1)\fP command line or some other equivalent
method.  However, it IS recommended to set the \fBUNITY_BUILD\fP target
property to false if it is known that enabling unity builds for the
target can lead to problems.
.UNINDENT
.UNINDENT
.SS ODR (One definition rule) errors
.sp
When multiple source files are included into one source file, as is done
for unity builds, it can potentially lead to ODR errors.  CMake provides
a number of measures to help address such problems:
.INDENT 0.0
.IP \(bu 2
Any source file that has a non\-empty \fI\%COMPILE_OPTIONS\fP,
\fI\%COMPILE_DEFINITIONS\fP, \fI\%COMPILE_FLAGS\fP, or
\fI\%INCLUDE_DIRECTORIES\fP source property will not be combined
into a unity source.
.IP \(bu 2
Any source file which is scanned for C++ module sources via
\fI\%CXX_SCAN_FOR_MODULES\fP, \fI\%CXX_SCAN_FOR_MODULES\fP, or
membership of a \fBCXX_MODULES\fP file set will not be combined into a unity
source.  See \fI\%cmake\-cxxmodules(7)\fP for details.
.IP \(bu 2
Projects can prevent an individual source file from being combined into
a unity source by setting its \fI\%SKIP_UNITY_BUILD_INCLUSION\fP
source property to true.  This can be a more effective way to prevent
problems with specific files than disabling unity builds for an entire
target.
.IP \(bu 2
Projects can set \fI\%UNITY_BUILD_UNIQUE_ID\fP to cause a valid
C\-identifier to be generated which is unique per file in a unity
build.  This can be used to avoid problems with anonymous namespaces
in unity builds.
.IP \(bu 2
The \fI\%UNITY_BUILD_CODE_BEFORE_INCLUDE\fP and
\fI\%UNITY_BUILD_CODE_AFTER_INCLUDE\fP target properties can be used
to inject code into the unity source files before and after every
\fB#include\fP statement.
.IP \(bu 2
The order of source files added to the target via commands like
\fI\%add_library()\fP, \fI\%add_executable()\fP or
\fI\%target_sources()\fP will be preserved in the generated unity source
files.  This can be used to manually enforce a specific grouping based on
the \fI\%UNITY_BUILD_BATCH_SIZE\fP target property.
.UNINDENT
.SS UNITY_BUILD_BATCH_SIZE
.sp
Added in version 3.16.

.sp
Specifies the maximum number of source files that can be combined into any one
unity source file when unity builds are enabled by the \fI\%UNITY_BUILD\fP
target property.  The original source files will be distributed across as many
unity source files as necessary to honor this limit.
.sp
The initial value for this property is taken from the
\fI\%CMAKE_UNITY_BUILD_BATCH_SIZE\fP variable when the target is created.
If that variable has not been set, the initial value will be 8.
.sp
The batch size needs to be selected carefully.  If set too high, the size of
the combined source files could result in the compiler using excessive memory
or hitting other similar limits.  In extreme cases, this can even result in
build failure.  On the other hand, if the batch size is too low, there will be
little gain in build performance.
.sp
Although strongly discouraged, the batch size may be set to a value of 0 to
combine all the sources for the target into a single unity file, regardless of
how many sources are involved.  This runs the risk of creating an excessively
large unity source file and negatively impacting the build performance, so
a value of 0 is not generally recommended.
.SS UNITY_BUILD_CODE_AFTER_INCLUDE
.sp
Added in version 3.16.

.sp
Code snippet which is included verbatim by the \fI\%UNITY_BUILD\fP
feature just after every \fB#include\fP statement in the generated unity
source files.  For example:
.INDENT 0.0
.INDENT 3.5
.sp
.EX
set(after [[
#if defined(NOMINMAX)
#undef NOMINMAX
#endif
]])
set_target_properties(myTarget PROPERTIES
  UNITY_BUILD_CODE_AFTER_INCLUDE \(dq${after}\(dq
)
.EE
.UNINDENT
.UNINDENT
.sp
See also \fI\%UNITY_BUILD_CODE_BEFORE_INCLUDE\fP\&.
.SS UNITY_BUILD_CODE_BEFORE_INCLUDE
.sp
Added in version 3.16.

.sp
Code snippet which is included verbatim by the \fI\%UNITY_BUILD\fP
feature just before every \fB#include\fP statement in the generated unity
source files.  For example:
.INDENT 0.0
.INDENT 3.5
.sp
.EX
set(before [[
#if !defined(NOMINMAX)
#define NOMINMAX
#endif
]])
set_target_properties(myTarget PROPERTIES
  UNITY_BUILD_CODE_BEFORE_INCLUDE \(dq${before}\(dq
)
.EE
.UNINDENT
.UNINDENT
.sp
See also \fI\%UNITY_BUILD_CODE_AFTER_INCLUDE\fP\&.
.SS UNITY_BUILD_MODE
.sp
Added in version 3.18.

.sp
CMake provides different algorithms for selecting which sources are grouped
together into a \fIbucket\fP\&. Selection is decided by this property,
which has the following acceptable values:
.INDENT 0.0
.TP
.B \fBBATCH\fP
When in this mode CMake determines which files are grouped together.
The \fI\%UNITY_BUILD_BATCH_SIZE\fP property controls the upper limit on
how many sources can be combined per unity source file.
.sp
Example usage:
.INDENT 7.0
.INDENT 3.5
.sp
.EX
add_library(example_library
            source1.cxx
            source2.cxx
            source3.cxx
            source4.cxx)

set_target_properties(example_library PROPERTIES
                      UNITY_BUILD_MODE BATCH
                      UNITY_BUILD_BATCH_SIZE 2
                      )
.EE
.UNINDENT
.UNINDENT
.TP
.B \fBGROUP\fP
When in this mode each target explicitly specifies how to group
source files. Each source file that has the same
\fI\%UNITY_GROUP\fP value will be grouped together. Any sources
that don\(aqt have this property will be compiled individually. The
\fI\%UNITY_BUILD_BATCH_SIZE\fP property is ignored when using
this mode.
.sp
Example usage:
.INDENT 7.0
.INDENT 3.5
.sp
.EX
add_library(example_library
            source1.cxx
            source2.cxx
            source3.cxx
            source4.cxx)

set_target_properties(example_library PROPERTIES
                      UNITY_BUILD_MODE GROUP
                      )

set_source_files_properties(source1.cxx source2.cxx source3.cxx
                            PROPERTIES UNITY_GROUP \(dqbucket1\(dq
                            )
set_source_files_properties(source4.cxx
                            PROPERTIES UNITY_GROUP \(dqbucket2\(dq
                            )
.EE
.UNINDENT
.UNINDENT
.UNINDENT
.sp
If no explicit \fBUNITY_BUILD_MODE\fP has been specified, CMake will
default to \fBBATCH\fP\&.
.SS UNITY_BUILD_RELOCATABLE
.sp
Added in version 4.0.

.sp
By default, the unity file generated when \fI\%UNITY_BUILD\fP is enabled
uses absolute paths to reference the original source files. This causes the
unity file to result in a different output depending on the location of the
source files.
.sp
When this property is set to true, the \fB#include\fP lines inside the generated
unity source files will attempt to use relative paths to the original source
files if possible in order to standardize the output of the unity file.
.sp
The unity file\(aqs path to an original source file uses the following priority:
.INDENT 0.0
.IP \(bu 2
a path relative to the generated unity file if the source file exists
directly in \fI\%CMAKE_BINARY_DIR\fP, or in a subfolder under it.
.IP \(bu 2
a path relative to \fI\%CMAKE_SOURCE_DIR\fP if the source file exists
directly in \fI\%CMAKE_SOURCE_DIR\fP, or in a subfolder under it.
.IP \(bu 2
an absolute path to the source file.
.UNINDENT
.sp
This target property \fIdoes not\fP guarantee a consistent unity file across
different environments as the final priority is an absolute path.
.sp
Example usage:
.INDENT 0.0
.INDENT 3.5
.sp
.EX
add_library(example_library
            source1.cxx
            source2.cxx
            source3.cxx)

set_target_properties(example_library PROPERTIES
                      UNITY_BUILD True
                      UNITY_BUILD_RELOCATABLE TRUE)
.EE
.UNINDENT
.UNINDENT
.SS UNITY_BUILD_UNIQUE_ID
.sp
Added in version 3.20.

.sp
The name of a valid C\-identifier which is set to a unique per\-file
value during unity builds.
.sp
When this property is populated and when \fI\%UNITY_BUILD\fP
is true, the property value is used to define a compiler definition
of the specified name. The value of the defined symbol is unspecified,
but it is unique per file path.
.sp
Given:
.INDENT 0.0
.INDENT 3.5
.sp
.EX
set_target_properties(myTarget PROPERTIES
  UNITY_BUILD \(dqON\(dq
  UNITY_BUILD_UNIQUE_ID \(dqMY_UNITY_ID\(dq
)
.EE
.UNINDENT
.UNINDENT
.sp
the \fBMY_UNITY_ID\fP symbol is defined to a unique per\-file value.
.sp
One known use case for this identifier is to disambiguate the
variables in an anonymous namespace in a limited scope.
Anonymous namespaces present a problem for unity builds because
they are used to ensure that certain variables and declarations
are scoped to a translation unit which is approximated by a
single source file.  When source files are combined in a unity
build file, those variables in different files are combined in
a single translation unit and the names clash.  This property can
be used to avoid that with code like the following:
.INDENT 0.0
.INDENT 3.5
.sp
.EX
// Needed for when unity builds are disabled
#ifndef MY_UNITY_ID
#define MY_UNITY_ID
#endif

namespace { namespace MY_UNITY_ID {
  // The name \(aqi\(aq clashes (or could clash) with other
  // variables in other anonymous namespaces
  int i = 42;
}}

int use_var()
{
  return MY_UNITY_ID::i;
}
.EE
.UNINDENT
.UNINDENT
.sp
The pseudonymous namespace is used within a truly anonymous namespace.
On many platforms, this maintains the invariant that the symbols within
do not get external linkage when performing a unity build.
.SS VERIFY_INTERFACE_HEADER_SETS
.sp
Added in version 3.24.

.sp
Used to verify that all headers in a target\(aqs \fBPUBLIC\fP and \fBINTERFACE\fP
header sets can be included on their own.
.sp
When this property is set to true, and the target is an object library, static
library, shared library, interface library, or executable with exports enabled,
and the target has one or more \fBPUBLIC\fP or \fBINTERFACE\fP header sets, an
object library target named \fB<target_name>_verify_interface_header_sets\fP is
created. This verification target has one source file per header in the
\fBPUBLIC\fP and \fBINTERFACE\fP header sets. Each source file only includes its
associated header file. The verification target links against the original
target to get all of its usage requirements. The verification target has its
\fI\%EXCLUDE_FROM_ALL\fP and \fI\%DISABLE_PRECOMPILE_HEADERS\fP
properties set to true, and its \fI\%AUTOMOC\fP, \fI\%AUTORCC\fP,
\fI\%AUTOUIC\fP, and \fI\%UNITY_BUILD\fP properties set to false.
.sp
If the header\(aqs \fI\%LANGUAGE\fP property is set, the value of that property
is used to determine the language with which to compile the header file.
Otherwise, if the target has any C++ sources, the header is compiled as C++.
Otherwise, if the target has any C sources, the header is compiled as C.
Otherwise, if C++ is enabled globally, the header is compiled as C++.
Otherwise, if C is enabled globally, the header is compiled as C. Otherwise,
the header file is not compiled.
.sp
If the header\(aqs \fI\%SKIP_LINTING\fP property is set to true, the file is
not compiled.
.sp
If any verification targets are created, a top\-level target called
\fBall_verify_interface_header_sets\fP is created which depends on all
verification targets.
.sp
This property is initialized by the value of the
\fI\%CMAKE_VERIFY_INTERFACE_HEADER_SETS\fP variable if it is set when
a target is created.
.sp
If the project wishes to control which header sets are verified by this
property, it can set \fI\%INTERFACE_HEADER_SETS_TO_VERIFY\fP\&.
.SS VERSION
.sp
Version number of a shared library target.
.sp
For shared libraries \fBVERSION\fP and \fI\%SOVERSION\fP can be used
to specify the build version and ABI version respectively.  When building or
installing appropriate symlinks are created if the platform supports
symlinks and the linker supports so\-names.  If only one of both is
specified the missing is assumed to have the same version number.  For
executables \fBVERSION\fP can be used to specify the build version.  When
building or installing appropriate symlinks are created if the
platform supports symlinks.
.sp
A common convention is to specify both \fBVERSION\fP and \fBSOVERSION\fP
such that \fBSOVERSION\fP matches the first component of \fBVERSION\fP:
.INDENT 0.0
.INDENT 3.5
.sp
.EX
set_target_properties(mylib PROPERTIES VERSION 1.2.3 SOVERSION 1)
.EE
.UNINDENT
.UNINDENT
.sp
The idea is that breaking changes to the ABI increment both the
\fBSOVERSION\fP and the major \fBVERSION\fP number.
.SS Windows Versions
.sp
For shared libraries and executables on Windows the \fBVERSION\fP
attribute is parsed to extract a \fB<major>.<minor>\fP version number.
These numbers are used as the image version of the binary.
.SS Mach\-O Versions
.sp
For shared libraries and executables on Mach\-O systems (e.g. macOS, iOS),
the \fI\%SOVERSION\fP property corresponds to the \fIcompatibility version\fP
and \fBVERSION\fP corresponds to the \fIcurrent version\fP (unless Mach\-O specific
overrides are provided, as discussed below).
See the \fI\%FRAMEWORK\fP target property for an example.
.sp
For shared libraries, the \fI\%MACHO_COMPATIBILITY_VERSION\fP and
\fI\%MACHO_CURRENT_VERSION\fP properties can be used to
override the \fIcompatibility version\fP and \fIcurrent version\fP respectively.
Note that \fI\%SOVERSION\fP will still be used to form the
\fBinstall_name\fP and both \fI\%SOVERSION\fP and \fBVERSION\fP may also
affect the file and symlink names.
.sp
Versions of Mach\-O binaries may be checked with the \fBotool \-L <binary>\fP
command.
.SS VISIBILITY_INLINES_HIDDEN
.sp
Whether to add a compile flag to hide symbols of inline functions
.sp
The \fBVISIBILITY_INLINES_HIDDEN\fP property determines whether a flag for
hiding symbols for inline functions, such as \fB\-fvisibility\-inlines\-hidden\fP,
should be used when invoking the compiler.  This property affects compilation
in sources of all types of targets.  See policy \fI\%CMP0063\fP\&.
.sp
This property is initialized by
the value of the \fI\%CMAKE_VISIBILITY_INLINES_HIDDEN\fP variable if it
is set when a target is created.
.SS VS_CONFIGURATION_TYPE
.sp
Added in version 3.6.

.sp
Visual Studio project configuration type.
.sp
Sets the \fBConfigurationType\fP attribute for a generated Visual Studio project.
The property value may use
\fI\%generator expressions\fP\&.
If this property is set, it overrides the default setting that is based on the
target type (e.g. \fBStaticLibrary\fP, \fBApplication\fP, ...).
.sp
Supported on \fI\%Visual Studio Generators\fP for VS 2010 and higher.
.SS VS_DEBUGGER_COMMAND
.sp
Added in version 3.12.

.sp
Sets the local debugger command for Visual Studio C++ targets.
The property value may use
\fI\%generator expressions\fP\&.
This is defined in \fB<LocalDebuggerCommand>\fP in the Visual Studio
project file.  This property is initialized by the value of the variable
\fI\%CMAKE_VS_DEBUGGER_COMMAND\fP if it is set when a target is
created.
.sp
This property only works for \fI\%Visual Studio Generators\fP;
it is ignored on other generators.
.SS VS_DEBUGGER_COMMAND_ARGUMENTS
.sp
Added in version 3.13.

.sp
Sets the local debugger command line arguments for Visual Studio C++ targets.
The property value may use
\fI\%generator expressions\fP\&.
This is defined in \fB<LocalDebuggerCommandArguments>\fP in the Visual Studio
project file.  This property is initialized by the value of the variable
\fI\%CMAKE_VS_DEBUGGER_COMMAND_ARGUMENTS\fP if it is set when a target is
created.
.sp
This property only works for \fI\%Visual Studio Generators\fP;
it is ignored on other generators.
.SS VS_DEBUGGER_ENVIRONMENT
.sp
Added in version 3.13.

.sp
Sets the local debugger environment for Visual Studio C++ targets.
The property value may use
\fI\%generator expressions\fP\&.
This is defined in \fB<LocalDebuggerEnvironment>\fP in the Visual Studio
project file.  This property is initialized by the value of the variable
\fI\%CMAKE_VS_DEBUGGER_ENVIRONMENT\fP if it is set when a target is
created.
.sp
This property only works for \fI\%Visual Studio Generators\fP;
it is ignored on other generators.
.SS VS_DEBUGGER_WORKING_DIRECTORY
.sp
Added in version 3.8.

.sp
Sets the local debugger working directory for Visual Studio C++ targets.
The property value may use
\fI\%generator expressions\fP\&.
This is defined in \fB<LocalDebuggerWorkingDirectory>\fP in the Visual Studio
project file.  This property is initialized by the value of the variable
\fI\%CMAKE_VS_DEBUGGER_WORKING_DIRECTORY\fP if it is set when a target is
created.
.sp
This property only works for \fI\%Visual Studio Generators\fP;
it is ignored on other generators.
.sp
See also \fI\%DEBUGGER_WORKING_DIRECTORY\fP\&.
.SS VS_DESKTOP_EXTENSIONS_VERSION
.sp
Added in version 3.4.

.sp
Visual Studio Windows 10 Desktop Extensions Version
.sp
Specifies the version of the Desktop Extensions that should be included in the
target. For example \fB10.0.10240.0\fP\&. If the value is not specified, the Desktop
Extensions will not be included. To use the same version of the extensions as
the Windows 10 SDK that is being used, you can use the
\fI\%CMAKE_VS_WINDOWS_TARGET_PLATFORM_VERSION\fP variable.
.SS VS_DOTNET_DOCUMENTATION_FILE
.sp
Added in version 3.17.

.sp
Visual Studio managed project .NET documentation output
.sp
Sets the target XML documentation file output.
.SS VS_DOTNET_REFERENCE_<refname>
.sp
Added in version 3.8.

.sp
Visual Studio managed project .NET reference with name \fB<refname>\fP
and hint path.
.sp
Adds one .NET reference to generated Visual Studio project. The
reference will have the name \fB<refname>\fP and will point to the
assembly given as value of the property.
.sp
See also \fI\%VS_DOTNET_REFERENCES\fP and
\fI\%VS_DOTNET_REFERENCES_COPY_LOCAL\fP
.SS VS_DOTNET_REFERENCEPROP_<refname>_TAG_<tagname>
.sp
Added in version 3.10.

.sp
Defines an XML property \fB<tagname>\fP for a .NET reference
\fB<refname>\fP\&.
.sp
Reference properties can be set for .NET references which are
defined by the target properties \fI\%VS_DOTNET_REFERENCES\fP,
\fI\%VS_DOTNET_REFERENCE_<refname>\fP
and also for project references to other C# targets which are
established by \fI\%target_link_libraries()\fP\&.
.sp
This property is only applicable to C# targets and Visual Studio
generators 2010 and later.
.SS VS_DOTNET_REFERENCES
.sp
Visual Studio managed project .NET references
.sp
Adds one or more semicolon\-delimited .NET references to a generated
Visual Studio project.  For example, \(dqSystem;System.Windows.Forms\(dq.
.SS VS_DOTNET_REFERENCES_COPY_LOCAL
.sp
Added in version 3.8.

.sp
Sets the \fBCopy Local\fP property for all .NET hint references in the target
.sp
Boolean property to enable/disable copying of .NET hint references to
output directory. The default is \fBON\fP\&.
.SS VS_DOTNET_STARTUP_OBJECT
.sp
Added in version 3.24.

.sp
Sets the startup object property in Visual Studio .NET targets.
The property value defines a full qualified class name (including package
name), for example: \fBMyCompany.Package.MyStarterClass\fP\&.
.sp
If the property is unset, Visual Studio uses the first matching
\fBstatic void Main(string[])\fP function signature by default. When more
than one \fBMain()\fP method is available in the current project, the property
becomes mandatory for building the project.
.sp
This property only works for \fI\%Visual Studio Generators\fP;
it is ignored on other generators.
.INDENT 0.0
.INDENT 3.5
.sp
.EX
set_property(TARGET ${TARGET_NAME} PROPERTY
  VS_DOTNET_STARTUP_OBJECT \(dqMyCompany.Package.MyStarterClass\(dq)
.EE
.UNINDENT
.UNINDENT
.SS VS_DOTNET_TARGET_FRAMEWORK_VERSION
.sp
Specify the .NET target framework version.
.sp
Used to specify the .NET target framework version for C++/CLI. For
example, \(dqv4.5\(dq.
.sp
This property is deprecated and should not be used anymore. Use
\fI\%DOTNET_TARGET_FRAMEWORK\fP or
\fI\%DOTNET_TARGET_FRAMEWORK_VERSION\fP instead.
.SS VS_DPI_AWARE
.sp
Added in version 3.16.

.sp
Set the Manifest Tool \-> Input and Output \-> DPI Awareness in the Visual Studio
target project properties.
.sp
Valid values are \fBPerMonitor\fP, \fBON\fP, or \fBOFF\fP\&.
.sp
For example:
.INDENT 0.0
.INDENT 3.5
.sp
.EX
add_executable(myproject myproject.cpp)
set_property(TARGET myproject PROPERTY VS_DPI_AWARE \(dqPerMonitor\(dq)
.EE
.UNINDENT
.UNINDENT
.SS VS_FRAMEWORK_REFERENCES
.sp
Added in version 3.31.

.sp
Visual Studio framework references.
Specify a \fI\%semicolon\-separated list\fP of framework references
to be added to a generated Visual Studio project. For example:
.INDENT 0.0
.IP \(bu 2
\(dqMicrosoft.WindowsDesktop.App.WPF\(dq for WPF applications
.IP \(bu 2
\(dqMicrosoft.WindowsDesktop.App.WindowsForms\(dq for WinForms applications
.IP \(bu 2
\(dqMicrosoft.WindowsDesktop.App\(dq for applications using both frameworks
.UNINDENT
.SS VS_GLOBAL_KEYWORD
.sp
Visual Studio project keyword.
.sp
Sets the \(dqkeyword\(dq attribute for a generated Visual Studio project.
Defaults to \(dqWin32Proj\(dq.  You may wish to override this value with
\(dqManagedCProj\(dq, for example, in a Visual Studio managed C++ unit test
project.
.SS VS_GLOBAL_PROJECT_TYPES
.sp
Visual Studio project type(s).
.sp
Can be set to one or more UUIDs recognized by Visual Studio to
indicate the type of project.  This value is copied verbatim into the
generated project file.  Example for a managed C++ unit testing
project:
.INDENT 0.0
.INDENT 3.5
.sp
.EX
{3AC096D0\-A1C2\-E12C\-1390\-A8335801FDAB};{8BC9CEB8\-8B4A\-11D0\-8D11\-00A0C91BC942}
.EE
.UNINDENT
.UNINDENT
.sp
UUIDs are semicolon\-delimited.
.SS VS_GLOBAL_ROOTNAMESPACE
.sp
Visual Studio project root namespace.
.sp
Sets the \(dqRootNamespace\(dq attribute for a generated Visual Studio
project.  The attribute will be generated only if this is set.
.SS VS_GLOBAL_<variable>
.sp
Visual Studio project\-specific global variable.
.sp
Tell the \fI\%Visual Studio Generators\fP to set the global variable
\fB<variable>\fP to a given value in the generated Visual Studio project.
Ignored on other generators.  For example, Qt integration works better if
\fBVS_GLOBAL_QtVersion\fP is set to the version \fBFindQt4.cmake\fP found.  For
example, \fB4.7.3\fP
.SS VS_IOT_EXTENSIONS_VERSION
.sp
Added in version 3.4.

.sp
Visual Studio Windows 10 IoT Extensions Version
.sp
Specifies the version of the IoT Extensions that should be included in the
target. For example \fB10.0.10240.0\fP\&. If the value is not specified, the IoT
Extensions will not be included. To use the same version of the extensions as
the Windows 10 SDK that is being used, you can use the
\fI\%CMAKE_VS_WINDOWS_TARGET_PLATFORM_VERSION\fP variable.
.SS VS_IOT_STARTUP_TASK
.sp
Added in version 3.4.

.sp
Visual Studio Windows 10 IoT Continuous Background Task
.sp
Specifies that the target should be compiled as a Continuous Background Task library.
.SS VS_JUST_MY_CODE_DEBUGGING
.sp
Added in version 3.15.

.sp
Enable Just My Code with Visual Studio debugger.
.sp
Supported on \fI\%Visual Studio Generators\fP for VS 2010 and higher,
\fI\%Makefile Generators\fP and the \fI\%Ninja\fP generators.
.sp
This property is initialized by the \fI\%CMAKE_VS_JUST_MY_CODE_DEBUGGING\fP
variable if it is set when a target is created.
.SS VS_KEYWORD
.sp
Removed.  This once specified the Visual Studio project keyword
for the \fI\%Visual Studio 9 2008\fP generator, and older,
but all of those generators have been removed.
.sp
Use the \fI\%VS_GLOBAL_KEYWORD\fP target property to set the
keyword for remaining \fI\%Visual Studio Generators\fP\&.
.SS VS_MOBILE_EXTENSIONS_VERSION
.sp
Added in version 3.4.

.sp
Visual Studio Windows 10 Mobile Extensions Version
.sp
Specifies the version of the Mobile Extensions that should be included in the
target. For example \fB10.0.10240.0\fP\&. If the value is not specified, the Mobile
Extensions will not be included. To use the same version of the extensions as
the Windows 10 SDK that is being used, you can use the
\fI\%CMAKE_VS_WINDOWS_TARGET_PLATFORM_VERSION\fP variable.
.SS VS_NO_COMPILE_BATCHING
.sp
Added in version 3.24.

.sp
Turn off compile batching for the target. Usually MSBuild calls the compiler
with multiple c/cpp files and compiler starts subprocesses for each file to
make the build parallel. If you want compiler to be invoked with one file at
a time set \fBVS_NO_COMPILE_BATCHING\fP to ON. If this flag is set MSBuild will
call compiler with one c/cpp file at a time. Useful when you want to use tool
that replaces the compiler, for example some build caching tool.
.sp
This property is initialized by the \fI\%CMAKE_VS_NO_COMPILE_BATCHING\fP
variable if it is set when a target is created.
.SS Example
.sp
This shows setting the property for the target \fBfoo\fP\&.
.INDENT 0.0
.INDENT 3.5
.sp
.EX
add_library(foo SHARED foo.cpp)
set_property(TARGET foo PROPERTY VS_NO_COMPILE_BATCHING ON)
.EE
.UNINDENT
.UNINDENT
.SS VS_NO_SOLUTION_DEPLOY
.sp
Added in version 3.15.

.sp
Specify that the target should not be marked for deployment to a Windows CE
or Windows Phone device in the generated Visual Studio solution.
.sp
Be default, all EXE and shared library (DLL) targets are marked to deploy to
the target device in the generated Visual Studio solution.
.sp
Generator expressions are supported.
.sp
There are reasons one might want to exclude a target / generated project from
deployment:
.INDENT 0.0
.IP \(bu 2
The library or executable may not be necessary in the primary deploy/debug
scenario, and excluding from deployment saves time in the
develop/download/debug cycle.
.IP \(bu 2
There may be insufficient space on the target device to accommodate all of
the build products.
.IP \(bu 2
Visual Studio 2013 requires a target device IP address be entered for each
target marked for deployment.  For large numbers of targets, this can be
tedious.
NOTE: Visual Studio \fIwill\fP deploy all project dependencies of a project
tagged for deployment to the IP address configured for that project even
if those dependencies are not tagged for deployment.
.UNINDENT
.SS Example 1
.sp
This shows setting the variable for the target foo.
.INDENT 0.0
.INDENT 3.5
.sp
.EX
add_library(foo SHARED foo.cpp)
set_property(TARGET foo PROPERTY VS_NO_SOLUTION_DEPLOY ON)
.EE
.UNINDENT
.UNINDENT
.SS Example 2
.sp
This shows setting the variable for the Release configuration only.
.INDENT 0.0
.INDENT 3.5
.sp
.EX
add_library(foo SHARED foo.cpp)
set_property(TARGET foo PROPERTY VS_NO_SOLUTION_DEPLOY \(dq$<CONFIG:Release>\(dq)
.EE
.UNINDENT
.UNINDENT
.SS VS_PACKAGE_REFERENCES
.sp
Added in version 3.15.

.sp
Visual Studio package references for nuget.
.sp
Adds one or more semicolon\-delimited package references to a generated
Visual Studio project. The version of the package will be
underscore delimited. For example, \fBboost_1.7.0;nunit_3.12.*\fP\&.
.INDENT 0.0
.INDENT 3.5
.sp
.EX
set_property(TARGET ${TARGET_NAME} PROPERTY
  VS_PACKAGE_REFERENCES \(dqboost_1.7.0\(dq)
.EE
.UNINDENT
.UNINDENT
.SS VS_PLATFORM_TOOLSET
.sp
Added in version 3.18.

.sp
Overrides the platform toolset used to build a target.
.sp
Only supported when the compiler used by the given toolset is the
same as the compiler used to build the whole source tree.
.sp
This is especially useful to create driver projects with the toolsets
\(dqWindowsUserModeDriver10.0\(dq or \(dqWindowsKernelModeDriver10.0\(dq.
.SS VS_PROJECT_IMPORT
.sp
Added in version 3.15.

.sp
Visual Studio managed project imports
.sp
Adds to a generated Visual Studio project one or more paths to \fB\&.props\fP
files needed when building projects from some NuGet packages.
.sp
For example:
.INDENT 0.0
.INDENT 3.5
.sp
.EX
set_property(TARGET myTarget PROPERTY VS_PROJECT_IMPORT
  \(dqmy_packages_path/PackageA.1.0.0/build/PackageA.props\(dq
  \(dqmy_packages_path/PackageB.1.0.0/build/PackageB.props\(dq
)
.EE
.UNINDENT
.UNINDENT
.SS VS_SCC_AUXPATH
.sp
Visual Studio Source Code Control Aux Path.
.sp
Can be set to change the visual studio source code control auxpath
property.
.SS VS_SCC_LOCALPATH
.sp
Visual Studio Source Code Control Local Path.
.sp
Can be set to change the visual studio source code control local path
property.
.SS VS_SCC_PROJECTNAME
.sp
Visual Studio Source Code Control Project.
.sp
Can be set to change the visual studio source code control project
name property.
.SS VS_SCC_PROVIDER
.sp
Visual Studio Source Code Control Provider.
.sp
Can be set to change the visual studio source code control provider
property.
.SS VS_SDK_REFERENCES
.sp
Added in version 3.7.

.sp
Visual Studio project SDK references.
Specify a \fI\%semicolon\-separated list\fP of SDK references
to be added to a generated Visual Studio project, e.g.
\fBMicrosoft.AdMediatorWindows81, Version=1.0\fP\&.
.SS VS_SOLUTION_DEPLOY
.sp
Added in version 3.18.

.sp
Specify that the target should be marked for deployment when not targeting
Windows CE, Windows Phone or a Windows Store application.
.sp
If the target platform doesn\(aqt support deployment, this property won\(aqt have
any effect.
.sp
\fI\%Generator expressions\fP are supported.
.SS Examples
.sp
Always deploy target \fBfoo\fP:
.INDENT 0.0
.INDENT 3.5
.sp
.EX
add_executable(foo SHARED foo.cpp)
set_property(TARGET foo PROPERTY VS_SOLUTION_DEPLOY ON)
.EE
.UNINDENT
.UNINDENT
.sp
Deploy target \fBfoo\fP for all configurations except \fBRelease\fP:
.INDENT 0.0
.INDENT 3.5
.sp
.EX
add_executable(foo SHARED foo.cpp)
set_property(TARGET foo PROPERTY VS_SOLUTION_DEPLOY \(dq$<NOT:$<CONFIG:Release>>\(dq)
.EE
.UNINDENT
.UNINDENT
.SS VS_SOURCE_SETTINGS_<tool>
.sp
Added in version 3.18.

.sp
Set any item metadata on all non\-built files that use <tool>.
.sp
Takes a list of \fBKey=Value\fP pairs. Tells the \fI\%Visual Studio Generators\fP
to set \fBKey\fP to \fBValue\fP as item metadata on all non\-built files
that use \fB<tool>\fP\&.
.sp
For example:
.INDENT 0.0
.INDENT 3.5
.sp
.EX
set_property(TARGET main PROPERTY VS_SOURCE_SETTINGS_FXCompile \(dqKey=Value\(dq \(dqKey2=Value2\(dq)
.EE
.UNINDENT
.UNINDENT
.sp
will set \fBKey\fP to \fBValue\fP and \fBKey2\fP to \fBValue2\fP for all
non\-built files that use \fBFXCompile\fP\&.
.sp
\fI\%Generator expressions\fP are supported.
.SS VS_USE_DEBUG_LIBRARIES
.sp
Added in version 3.30.

.sp
Indicate to \fI\%Visual Studio Generators\fP what configurations are considered
debug configurations.  This controls the \fBUseDebugLibraries\fP setting in
each configuration of a \fB\&.vcxproj\fP file.
.sp
The \(dqUse Debug Libraries\(dq setting in Visual Studio projects, despite its
specific\-sounding name, is a general\-purpose indicator of what configurations
are considered debug configurations.  In standalone projects, this may affect
MSBuild\(aqs default selection of MSVC runtime library, optimization flags,
runtime checks, and similar settings.  In CMake projects those settings are
typically generated explicitly based on the project\(aqs specification, e.g.,
the MSVC runtime library is controlled by \fI\%MSVC_RUNTIME_LIBRARY\fP\&.  However,
the \fBUseDebugLibraries\fP indicator is useful for reference by both humans
and tools, and may also affect the behavior of platform\-specific SDKs.
.sp
Set \fBVS_USE_DEBUG_LIBRARIES\fP to a true or false value to indicate whether
each configuration is considered a debug configuration.  The value may also
be the empty string (\fB\(dq\(dq\fP) in which case no \fBUseDebugLibraries\fP will be
added explicitly by CMake, and MSBuild will use its default value, \fBfalse\fP\&.
.sp
Use \fI\%generator expressions\fP
for per\-configuration specification.  For example, the code:
.INDENT 0.0
.INDENT 3.5
.sp
.EX
add_executable(foo foo.c)
set_property(TARGET foo PROPERTY
  VS_USE_DEBUG_LIBRARIES \(dq$<CONFIG:Debug,Custom>\(dq)
.EE
.UNINDENT
.UNINDENT
.sp
indicates that target \fBfoo\fP considers its \(dqDebug\(dq and \(dqCustom\(dq
configurations to be debug configurations, and its other configurations
to be non\-debug configurations.
.sp
The property is initialized from the value of the
\fI\%CMAKE_VS_USE_DEBUG_LIBRARIES\fP variable, if it is set.
If the property is not set then CMake generates \fBUseDebugLibraries\fP using
heuristics to determine which configurations are debug configurations.
See policy \fI\%CMP0162\fP\&.
.SS VS_USER_PROPS
.sp
Added in version 3.8.

.sp
Sets the user props file to be included in the visual studio
C++ project file. The standard path is
\fB$(UserRootDir)\e\eMicrosoft.Cpp.$(Platform).user.props\fP, which is
in most cases the same as
\fB%LOCALAPPDATA%\e\eMicrosoft\e\eMSBuild\e\ev4.0\e\eMicrosoft.Cpp.Win32.user.props\fP
or \fB%LOCALAPPDATA%\e\eMicrosoft\e\eMSBuild\e\ev4.0\e\eMicrosoft.Cpp.x64.user.props\fP\&.
.sp
The \fB*.user.props\fP files can be used for Visual Studio wide
configuration which is independent from cmake.
.SS VS_FILTER_PROPS
.sp
Added in version 3.30.

.sp
Sets the filter props file to be included in the visual studio
C++ project filter file.
.sp
The \fB*.filter.props\fP files can be used for Visual Studio wide
configuration which is independent from cmake.
.SS VS_WINDOWS_TARGET_PLATFORM_MIN_VERSION
.sp
Added in version 3.4.

.sp
Visual Studio Windows Target Platform Minimum Version
.sp
For Windows 10. Specifies the minimum version of the OS that is being
targeted. For example \fB10.0.10240.0\fP\&. If the value is not specified, the
value of the \fI\%CMAKE_VS_WINDOWS_TARGET_PLATFORM_VERSION\fP variable
will be used on WindowsStore projects.  Otherwise the target platform
minimum version will not be specified for the project.
.sp
Added in version 3.27: This property is initialized by the value of the
\fI\%CMAKE_VS_WINDOWS_TARGET_PLATFORM_MIN_VERSION\fP variable
if it is set when a target is created.

.SS VS_WINRT_COMPONENT
.sp
Added in version 3.1.

.sp
Mark a target as a Windows Runtime component for the \fI\%Visual Studio Generators\fP\&.
Compile the target with \fBC++/CX\fP language extensions for Windows Runtime.
For \fBSHARED\fP and \fBMODULE\fP libraries, this also defines the
\fB_WINRT_DLL\fP preprocessor macro.
.sp
\fBNOTE:\fP
.INDENT 0.0
.INDENT 3.5
Currently this is implemented only by \fI\%Visual Studio Generators\fP\&.
Support may be added to other generators in the future.
.UNINDENT
.UNINDENT
.SS VS_WINRT_REFERENCES
.sp
Visual Studio project Windows Runtime Metadata references
.sp
Adds one or more semicolon\-delimited WinRT references to a generated
Visual Studio project.  For example, \(dqWindows;Windows.UI.Core\(dq.
.SS WATCOM_RUNTIME_LIBRARY
.sp
Added in version 3.24.

.sp
Select the Watcom runtime library for use by compilers targeting the Watcom ABI.
.sp
The allowed values are:
.INDENT 0.0
.TP
.B \fBSingleThreaded\fP
Compile without additional flags to use a single\-threaded
statically\-linked runtime library.
.TP
.B \fBSingleThreadedDLL\fP
Compile with \fB\-br\fP or equivalent flag(s) to use a single\-threaded
dynamically\-linked runtime library. This is not available for Linux
targets.
.TP
.B \fBMultiThreaded\fP
Compile with \fB\-bm\fP or equivalent flag(s) to use a multi\-threaded
statically\-linked runtime library.
.TP
.B \fBMultiThreadedDLL\fP
Compile with \fB\-bm \-br\fP or equivalent flag(s) to use a multi\-threaded
dynamically\-linked runtime library. This is not available for Linux
targets.
.UNINDENT
.sp
The value is ignored on non\-Watcom compilers but an unsupported value will
be rejected as an error when using a compiler targeting the Watcom ABI.
.sp
The value may also be the empty string (\fB\(dq\(dq\fP) in which case no runtime
library selection flag will be added explicitly by CMake.
.sp
Use \fI\%generator expressions\fP to
support per\-configuration specification.
.sp
For example, the code:
.INDENT 0.0
.INDENT 3.5
.sp
.EX
add_executable(foo foo.c)
set_property(TARGET foo PROPERTY
  WATCOM_RUNTIME_LIBRARY \(dqMultiThreaded\(dq)
.EE
.UNINDENT
.UNINDENT
.sp
selects for the target \fBfoo\fP a multi\-threaded statically\-linked runtime
library.
.sp
If this property is not set then CMake uses the default value
\fBMultiThreadedDLL\fP on Windows and \fBSingleThreaded\fP on other
platforms to select a Watcom runtime library.
.sp
\fBNOTE:\fP
.INDENT 0.0
.INDENT 3.5
This property has effect only when policy \fI\%CMP0136\fP is set to \fBNEW\fP
prior to the first \fI\%project()\fP or \fI\%enable_language()\fP command
that enables a language using a compiler targeting the Watcom ABI.
.UNINDENT
.UNINDENT
.SS WIN32_EXECUTABLE
.sp
Build an executable with a WinMain entry point on windows.
.sp
When this property is set to true the executable when linked on
Windows will be created with a WinMain() entry point instead of just
main().  This makes it a GUI executable instead of a console application.
See the \fI\%CMAKE_MFC_FLAG\fP variable documentation to
configure use of the Microsoft Foundation Classes (MFC) for WinMain
executables.  This property is initialized by the value of the
\fI\%CMAKE_WIN32_EXECUTABLE\fP variable if it is set when
a target is created.
.sp
This property supports
\fI\%generator expressions\fP, except if the
target is managed (contains C# code.)
.SS WINDOWS_EXPORT_ALL_SYMBOLS
.sp
Added in version 3.4.

.sp
This property is implemented only for MS\-compatible tools on Windows.
.sp
Enable this boolean property to automatically create a module definition
(\fB\&.def\fP) file with all global symbols found in the input \fB\&.obj\fP files
for a \fBSHARED\fP library (or executable with \fI\%ENABLE_EXPORTS\fP)
on Windows.  The module definition file will be passed to the linker
causing all symbols to be exported from the \fB\&.dll\fP\&.
.sp
This simplifies porting projects to Windows by reducing the need for
explicit \fBdllexport\fP markup, even in \fBC++\fP classes.  Function
symbols will be automatically exported and may be linked by callers.
However, there are some cases when compiling code in a consumer may
require explicit \fBdllimport\fP markup:
.INDENT 0.0
.IP \(bu 2
Global \fIdata\fP symbols must be explicitly marked with
\fB__declspec(dllimport)\fP in order to link to data in the \fB\&.dll\fP\&.
.IP \(bu 2
In cases that the compiler generates references to the virtual function
table, such as in a delegating constructor of a class with virtual
functions, the whole class must be marked with \fB__declspec(dllimport)\fP
in order to link to the vftable in the \fB\&.dll\fP\&.
.IP \(bu 2
See the \X'tty: link https://learn.microsoft.com/en-us/cpp/build/reference/export-exports-a-function'\fI\%MSVC Linker /EXPORT Option\fP\X'tty: link' for more information on data symbols.
.UNINDENT
.sp
When this property is enabled, zero or more \fB\&.def\fP files may also be
specified as source files of the target.  The exports named by these files
will be merged with those detected from the object files to generate a
single module definition file to be passed to the linker.  This can be
used to export symbols from a \fB\&.dll\fP that are not in any of its object
files but are added by the linker from dependencies (e.g. \fBmsvcrt.lib\fP).
.sp
This property is initialized by the value of
the \fI\%CMAKE_WINDOWS_EXPORT_ALL_SYMBOLS\fP variable if it is set
when a target is created.
.SS XCODE_ATTRIBUTE_<an\-attribute>
.sp
Set Xcode target attributes directly.
.sp
Tell the \fI\%Xcode\fP generator to set \fB<an\-attribute>\fP to a given
value in the generated Xcode project.  Ignored on other generators.
.sp
This offers low\-level control over the generated Xcode project file.
It is meant as a last resort for specifying settings that CMake does
not otherwise have a way to control.  Although this can override a
setting CMake normally produces on its own, doing so bypasses CMake\(aqs
model of the project and can break things.
.sp
See the \fI\%CMAKE_XCODE_ATTRIBUTE_<an\-attribute>\fP variable
to set attributes on all targets in a directory tree.
.sp
Contents of \fBXCODE_ATTRIBUTE_<an\-attribute>\fP may use
\(dqgenerator expressions\(dq with the syntax \fB$<...>\fP\&.  See the
\fI\%cmake\-generator\-expressions(7)\fP manual for available
expressions.  See the \fI\%cmake\-buildsystem(7)\fP manual
for more on defining buildsystem properties.
.SS XCODE_EMBED_FRAMEWORKS_CODE_SIGN_ON_COPY
.sp
Added in version 3.20.

.sp
Tell the \fI\%Xcode\fP generator to perform code signing for all the
frameworks and libraries that are embedded using the
\fI\%XCODE_EMBED_FRAMEWORKS\fP property.
.sp
Added in version 3.21.

.sp
This property was generalized to other types of embedded items.  See
\fI\%XCODE_EMBED_<type>_CODE_SIGN_ON_COPY\fP for the more general form.
.SS XCODE_EMBED_FRAMEWORKS_REMOVE_HEADERS_ON_COPY
.sp
Added in version 3.20.

.sp
Tell the \fI\%Xcode\fP generator to remove headers from all the
frameworks that are embedded using the
\fI\%XCODE_EMBED_FRAMEWORKS\fP property.
.sp
Added in version 3.21.

.sp
This property was generalized to other types of embedded items.  See
\fI\%XCODE_EMBED_<type>_REMOVE_HEADERS_ON_COPY\fP for the more
general form.
.SS XCODE_EMBED_<type>
.sp
Added in version 3.20.

.sp
Tell the \fI\%Xcode\fP generator to embed the specified list of items into
the target bundle.  \fB<type>\fP specifies the embed build phase to use.
See the Xcode documentation for the base location of each \fB<type>\fP\&.
.sp
The supported values for \fB<type>\fP are:
.INDENT 0.0
.TP
.B \fBFRAMEWORKS\fP
The specified items will be added to the \fBEmbed Frameworks\fP build phase.
The items can be CMake target names or paths to frameworks or libraries.
.TP
.B \fBAPP_EXTENSIONS\fP
Added in version 3.21.

.sp
The specified items will be added to the \fBEmbed App Extensions\fP build
phase, with \fBDestination\fP set to \fBPlugIns and Foundation Extensions\fP
They must be CMake target names.
.TP
.B \fBEXTENSIONKIT_EXTENSIONS\fP
Added in version 3.26.

.sp
The specified items will be added to the \fBEmbed App Extensions\fP build
phase, with \fBDestination\fP set to \fBExtensionKit Extensions\fP
They must be CMake target names, and should likely have the
\fBXCODE_PRODUCT_TYPE\fP target property set to
\fBcom.apple.product\-type.extensionkit\-extension\fP
as well as the  \fBXCODE_EXPLICIT_FILE_TYPE\fP to
\fBwrapper.extensionkit\-extension\fP
.TP
.B \fBPLUGINS\fP
Added in version 3.23.

.sp
The specified items will be added to the \fBEmbed PlugIns\fP build phase.
They must be CMake target names.
.TP
.B \fBRESOURCES\fP
Added in version 3.28.

.sp
The specified items will be added to the \fBEmbed Resources\fP build phase.
They must be CMake target names or folder paths.
.TP
.B \fBXPC_SERVICES\fP
Added in version 3.29.

.sp
The specified items will be added to the \fBEmbed XPC Services\fP build phase.
They must be CMake target names.
.UNINDENT
.sp
When listing a target as any of the things to embed, Xcode must see that target
as part of the same Xcode project, or a sub\-project of the one defining the
bundle.  In order to satisfy this constraint, the CMake project must ensure
at least one of the following:
.INDENT 0.0
.IP \(bu 2
The \fI\%CMAKE_XCODE_GENERATE_TOP_LEVEL_PROJECT_ONLY\fP variable is set
to true in the top level \fBCMakeLists.txt\fP file.  This is the simplest and
most robust approach.
.IP \(bu 2
Define the target\-to\-embed in a subdirectory of the one that defines the
target being embedded into.
.IP \(bu 2
If the target\-to\-embed and the target being embedded into are in separate,
unrelated directories (i.e. they are siblings, not one a parent of the
other), ensure they have a common \fI\%project()\fP call in a parent
directory and no other \fI\%project()\fP calls between themselves and that
common \fI\%project()\fP call.
.UNINDENT
.sp
See also \fI\%XCODE_EMBED_<type>_PATH\fP,
\fI\%XCODE_EMBED_<type>_REMOVE_HEADERS_ON_COPY\fP and
\fI\%XCODE_EMBED_<type>_CODE_SIGN_ON_COPY\fP\&.
.SS XCODE_EMBED_<type>_CODE_SIGN_ON_COPY
.sp
Added in version 3.20.

.sp
Boolean property used only by the \fI\%Xcode\fP generator.  It specifies
whether to perform code signing for the items that are embedded using the
\fI\%XCODE_EMBED_<type>\fP property.
.sp
The supported values for \fB<type>\fP are:
.sp
\fBFRAMEWORKS\fP
.INDENT 0.0
.TP
.B \fBAPP_EXTENSIONS\fP
Added in version 3.21.

.TP
.B \fBEXTENSIONKIT_EXTENSIONS\fP
Added in version 3.26.

.TP
.B \fBPLUGINS\fP
Added in version 3.23.

.UNINDENT
.sp
If a \fBXCODE_EMBED_<type>_CODE_SIGN_ON_COPY\fP property is not defined on the
target, no code signing on copy will be performed for that \fB<type>\fP\&.
.SS XCODE_EMBED_<type>_PATH
.sp
Added in version 3.20.

.sp
This property is used only by the \fI\%Xcode\fP generator.  When defined,
it specifies the relative path to use when embedding the items specified by
\fI\%XCODE_EMBED_<type>\fP\&.  The path is relative
to the base location of the \fBEmbed XXX\fP build phase associated with
\fB<type>\fP\&.  See the Xcode documentation for the base location of each
\fB<type>\fP\&.
.sp
The supported values for \fB<type>\fP are:
.sp
\fBFRAMEWORKS\fP
.INDENT 0.0
.TP
.B \fBAPP_EXTENSIONS\fP
Added in version 3.21.

.TP
.B \fBEXTENSIONKIT_EXTENSIONS\fP
Added in version 3.26.

.TP
.B \fBPLUGINS\fP
Added in version 3.23.

.TP
.B \fBRESOURCES\fP
Added in version 3.28.

.TP
.B \fBXPC_SERVICES\fP
Added in version 3.29.

.UNINDENT
.SS XCODE_EMBED_<type>_REMOVE_HEADERS_ON_COPY
.sp
Added in version 3.20.

.sp
Boolean property used only by the \fI\%Xcode\fP generator.  It specifies
whether to remove headers from all the frameworks that are embedded using the
\fI\%XCODE_EMBED_<type>\fP property.
.sp
The supported values for \fB<type>\fP are:
.INDENT 0.0
.TP
.B \fBFRAMEWORKS\fP
If the \fBXCODE_EMBED_FRAMEWORKS_REMOVE_HEADERS_ON_COPY\fP property is not
defined, headers will not be removed on copy by default.
.TP
.B \fBAPP_EXTENSIONS\fP
Added in version 3.21.

.sp
If the \fBXCODE_EMBED_APP_EXTENSIONS_REMOVE_HEADERS_ON_COPY\fP property is not
defined, headers WILL be removed on copy by default.
.TP
.B \fBEXTENSIONKIT_EXTENSIONS\fP
Added in version 3.26.

.sp
If the \fBXCODE_EMBED_APP_EXTENSIONS_REMOVE_HEADERS_ON_COPY\fP property is not
defined, headers WILL be removed on copy by default.
.TP
.B \fBPLUGINS\fP
Added in version 3.23.

.UNINDENT
.SS XCODE_EXPLICIT_FILE_TYPE
.sp
Added in version 3.8.

.sp
Set the Xcode \fBexplicitFileType\fP attribute on its reference to a
target.  CMake computes a default based on target type but
can be told explicitly with this property.
.sp
See also \fI\%XCODE_PRODUCT_TYPE\fP\&.
.SS XCODE_GENERATE_SCHEME
.sp
Added in version 3.15.

.sp
If enabled, the \fI\%Xcode\fP generator will generate schema files.  These
are useful to invoke analyze, archive, build\-for\-testing and test
actions from the command line.
.sp
This property is initialized by the value of the variable
\fI\%CMAKE_XCODE_GENERATE_SCHEME\fP if it is set when a target
is created.
.sp
The following target properties overwrite the default of the
corresponding settings on the \(dqDiagnostic\(dq tab for each schema file.
Each of those is initialized by the respective \fBCMAKE_\fP variable
at target creation time.
.INDENT 0.0
.IP \(bu 2
\fI\%XCODE_SCHEME_ADDRESS_SANITIZER\fP
.IP \(bu 2
\fI\%XCODE_SCHEME_ADDRESS_SANITIZER_USE_AFTER_RETURN\fP
.IP \(bu 2
\fI\%XCODE_SCHEME_DISABLE_MAIN_THREAD_CHECKER\fP
.IP \(bu 2
\fI\%XCODE_SCHEME_DYNAMIC_LIBRARY_LOADS\fP
.IP \(bu 2
\fI\%XCODE_SCHEME_DYNAMIC_LINKER_API_USAGE\fP
.IP \(bu 2
\fI\%XCODE_SCHEME_GUARD_MALLOC\fP
.IP \(bu 2
\fI\%XCODE_SCHEME_MAIN_THREAD_CHECKER_STOP\fP
.IP \(bu 2
\fI\%XCODE_SCHEME_MALLOC_GUARD_EDGES\fP
.IP \(bu 2
\fI\%XCODE_SCHEME_MALLOC_SCRIBBLE\fP
.IP \(bu 2
\fI\%XCODE_SCHEME_MALLOC_STACK\fP
.IP \(bu 2
\fI\%XCODE_SCHEME_THREAD_SANITIZER\fP
.IP \(bu 2
\fI\%XCODE_SCHEME_THREAD_SANITIZER_STOP\fP
.IP \(bu 2
\fI\%XCODE_SCHEME_UNDEFINED_BEHAVIOUR_SANITIZER\fP
.IP \(bu 2
\fI\%XCODE_SCHEME_UNDEFINED_BEHAVIOUR_SANITIZER_STOP\fP
.IP \(bu 2
\fI\%XCODE_SCHEME_ENABLE_GPU_API_VALIDATION\fP
.IP \(bu 2
\fI\%XCODE_SCHEME_ENABLE_GPU_SHADER_VALIDATION\fP
.IP \(bu 2
\fI\%XCODE_SCHEME_ZOMBIE_OBJECTS\fP
.UNINDENT
.sp
The following target properties will be applied on the
\(dqInfo\(dq, \(dqArguments\(dq, and \(dqOptions\(dq tab:
.INDENT 0.0
.IP \(bu 2
\fI\%XCODE_SCHEME_ARGUMENTS\fP
.IP \(bu 2
\fI\%XCODE_SCHEME_DEBUG_AS_ROOT\fP
.IP \(bu 2
\fI\%XCODE_SCHEME_DEBUG_DOCUMENT_VERSIONING\fP
.IP \(bu 2
\fI\%XCODE_SCHEME_ENABLE_GPU_FRAME_CAPTURE_MODE\fP
.IP \(bu 2
\fI\%XCODE_SCHEME_ENVIRONMENT\fP
.IP \(bu 2
\fI\%XCODE_SCHEME_EXECUTABLE\fP
.IP \(bu 2
\fI\%XCODE_SCHEME_LAUNCH_CONFIGURATION\fP
.IP \(bu 2
\fI\%XCODE_SCHEME_LAUNCH_MODE\fP
.IP \(bu 2
\fI\%XCODE_SCHEME_TEST_CONFIGURATION\fP
.IP \(bu 2
\fI\%XCODE_SCHEME_LLDB_INIT_FILE\fP
.IP \(bu 2
\fI\%XCODE_SCHEME_WORKING_DIRECTORY\fP
.UNINDENT
.SS XCODE_LINK_BUILD_PHASE_MODE
.sp
Added in version 3.19.

.sp
When using the \fI\%Xcode\fP generator, libraries to be linked will be
specified in the Xcode project file using either the \(dqLink Binary With
Libraries\(dq build phase or directly as linker flags.  The former allows Xcode
to manage build paths, which may be necessary when creating Xcode archives
because it may use different build paths to a regular build.
.sp
This property controls usage of \(dqLink Binary With Libraries\(dq build phase for
a target that is an app bundle, executable, shared library, shared framework
or a module library.
.sp
Possible values are:
.INDENT 0.0
.IP \(bu 2
\fBNONE\fP
The libraries will be linked by specifying the linker flags directly.
.IP \(bu 2
\fBBUILT_ONLY\fP
The \(dqLink Binary With Libraries\(dq build phase will be used to link to another
target under the following conditions:
.INDENT 2.0
.IP \(bu 2
The target to be linked to is a regular non\-imported, non\-interface library
target.
.IP \(bu 2
The output directory of the target being built has not been changed from
its default (see \fI\%RUNTIME_OUTPUT_DIRECTORY\fP and
\fI\%LIBRARY_OUTPUT_DIRECTORY\fP).
.UNINDENT
.IP \(bu 2
\fBKNOWN_LOCATION\fP
The \(dqLink Binary With Libraries\(dq build phase will be used to link to another
target under the same conditions as with \fBBUILT_ONLY\fP and also:
.INDENT 2.0
.IP \(bu 2
Imported library targets except those of type \fBUNKNOWN\fP\&.
.IP \(bu 2
Any non\-target library specified directly with a path.
.UNINDENT
.UNINDENT
.sp
For all other cases, the libraries will be linked by specifying the linker
flags directly.
.sp
\fBWARNING:\fP
.INDENT 0.0
.INDENT 3.5
Libraries linked using \(dqLink Binary With Libraries\(dq are linked after the
ones linked through regular linker flags.  This order should be taken into
account when different static libraries contain symbols with the same name,
as the former ones will take precedence over the latter.
.UNINDENT
.UNINDENT
.sp
\fBWARNING:\fP
.INDENT 0.0
.INDENT 3.5
If two or more directories contain libraries with identical file names and
some libraries are linked from those directories, the library search path
lookup will end up linking libraries from the first directory.  This is a
known limitation of Xcode.
.UNINDENT
.UNINDENT
.sp
This property is initialized by the value of the
\fI\%CMAKE_XCODE_LINK_BUILD_PHASE_MODE\fP variable if it is set when a
target is created.
.SS XCODE_PRODUCT_TYPE
.sp
Added in version 3.8.

.sp
Set the Xcode \fBproductType\fP attribute on its reference to a
target.  CMake computes a default based on target type but
can be told explicitly with this property.
.sp
See also \fI\%XCODE_EXPLICIT_FILE_TYPE\fP\&.
.SS XCODE_SCHEME_ADDRESS_SANITIZER
.sp
Added in version 3.13.

.sp
Whether to enable \fBAddress Sanitizer\fP in the Diagnostics
section of the generated Xcode scheme.
.sp
This property is initialized by the value of the variable
\fI\%CMAKE_XCODE_SCHEME_ADDRESS_SANITIZER\fP if it is set
when a target is created.
.sp
Please refer to the \fI\%XCODE_GENERATE_SCHEME\fP target property
documentation to see all Xcode schema related properties.
.SS XCODE_SCHEME_ADDRESS_SANITIZER_USE_AFTER_RETURN
.sp
Added in version 3.13.

.sp
Whether to enable \fBDetect use of stack after return\fP
in the Diagnostics section of the generated Xcode scheme.
.sp
This property is initialized by the value of the variable
\fI\%CMAKE_XCODE_SCHEME_ADDRESS_SANITIZER_USE_AFTER_RETURN\fP
if it is set when a target is created.
.sp
Please refer to the \fI\%XCODE_GENERATE_SCHEME\fP target property
documentation to see all Xcode schema related properties.
.SS XCODE_SCHEME_ARGUMENTS
.sp
Added in version 3.13.

.sp
Specify command line arguments that should be added to the Arguments
section of the generated Xcode scheme.
.sp
If set to a list of arguments those will be added to the scheme.
.sp
Please refer to the \fI\%XCODE_GENERATE_SCHEME\fP target property
documentation to see all Xcode schema related properties.
.SS XCODE_SCHEME_DEBUG_AS_ROOT
.sp
Added in version 3.15.

.sp
Whether to debug the target as \(aqroot\(aq.
.sp
Please refer to the \fI\%XCODE_GENERATE_SCHEME\fP target property
documentation to see all Xcode schema related properties.
.SS XCODE_SCHEME_DEBUG_DOCUMENT_VERSIONING
.sp
Added in version 3.16.

.sp
Whether to enable
\fBAllow debugging when using document Versions Browser\fP
in the Options section of the generated Xcode scheme.
.sp
This property is initialized by the value of the variable
\fI\%CMAKE_XCODE_SCHEME_DEBUG_DOCUMENT_VERSIONING\fP
if it is set when a target is created.
.sp
Please refer to the \fI\%XCODE_GENERATE_SCHEME\fP target property
documentation to see all Xcode schema related properties.
.SS XCODE_SCHEME_DISABLE_MAIN_THREAD_CHECKER
.sp
Added in version 3.13.

.sp
Whether to disable the \fBMain Thread Checker\fP
in the Diagnostics section of the generated Xcode scheme.
.sp
This property is initialized by the value of the variable
\fI\%CMAKE_XCODE_SCHEME_DISABLE_MAIN_THREAD_CHECKER\fP
if it is set when a target is created.
.sp
Please refer to the \fI\%XCODE_GENERATE_SCHEME\fP target property
documentation to see all Xcode schema related properties.
.SS XCODE_SCHEME_DYNAMIC_LIBRARY_LOADS
.sp
Added in version 3.13.

.sp
Whether to enable \fBDynamic Library Loads\fP
in the Diagnostics section of the generated Xcode scheme.
.sp
This property is initialized by the value of the variable
\fI\%CMAKE_XCODE_SCHEME_DYNAMIC_LIBRARY_LOADS\fP if it is set
when a target is created.
.sp
Please refer to the \fI\%XCODE_GENERATE_SCHEME\fP target property
documentation to see all Xcode schema related properties.
.SS XCODE_SCHEME_DYNAMIC_LINKER_API_USAGE
.sp
Added in version 3.13.

.sp
Whether to enable \fBDynamic Linker API usage\fP
in the Diagnostics section of the generated Xcode scheme.
.sp
This property is initialized by the value of the variable
\fI\%CMAKE_XCODE_SCHEME_DYNAMIC_LINKER_API_USAGE\fP if it is set
when a target is created.
.sp
Please refer to the \fI\%XCODE_GENERATE_SCHEME\fP target property
documentation to see all Xcode schema related properties.
.SS XCODE_SCHEME_ENABLE_GPU_API_VALIDATION
.sp
Added in version 3.25.

.sp
Property value for \fBMetal: API Validation\fP in the Options section of
the generated Xcode scheme.
.sp
This property is initialized by the value of the variable
\fI\%CMAKE_XCODE_SCHEME_ENABLE_GPU_API_VALIDATION\fP
if it is set when a target is created.
.sp
Please refer to the \fI\%XCODE_GENERATE_SCHEME\fP target property
documentation to see all Xcode schema related properties.
.SS XCODE_SCHEME_ENABLE_GPU_FRAME_CAPTURE_MODE
.sp
Added in version 3.23.

.sp
Property value for \fBGPU Frame Capture\fP in the Options section of
the generated Xcode scheme. Example values are \fBMetal\fP and
\fBDisabled\fP\&.
.sp
This property is initialized by the value of the variable
\fI\%CMAKE_XCODE_SCHEME_ENABLE_GPU_FRAME_CAPTURE_MODE\fP
if it is set when a target is created.
.sp
Please refer to the \fI\%XCODE_GENERATE_SCHEME\fP target property
documentation to see all Xcode schema related properties.
.SS XCODE_SCHEME_ENABLE_GPU_SHADER_VALIDATION
.sp
Added in version 3.25.

.sp
Property value for \fBMetal: Shader Validation\fP in the Options section of
the generated Xcode scheme.
.sp
This property is initialized by the value of the variable
\fI\%CMAKE_XCODE_SCHEME_ENABLE_GPU_SHADER_VALIDATION\fP
if it is set when a target is created.
.sp
Please refer to the \fI\%XCODE_GENERATE_SCHEME\fP target property
documentation to see all Xcode schema related properties.
.SS XCODE_SCHEME_ENVIRONMENT
.sp
Added in version 3.13.

.sp
Specify environment variables that should be added to the Arguments
section of the generated Xcode scheme.
.sp
If set to a list of environment variables and values of the form
\fBMYVAR=value\fP those environment variables will be added to the
scheme.
.sp
Please refer to the \fI\%XCODE_GENERATE_SCHEME\fP target property
documentation to see all Xcode schema related properties.
.SS XCODE_SCHEME_EXECUTABLE
.sp
Added in version 3.13.

.sp
Specify path to executable in the Info section of the generated
Xcode scheme. If not set the schema generator will select the
current target if it is actually executable.
.sp
Please refer to the \fI\%XCODE_GENERATE_SCHEME\fP target property
documentation to see all Xcode schema related properties.
.SS XCODE_SCHEME_GUARD_MALLOC
.sp
Added in version 3.13.

.sp
Whether to enable \fBGuard Malloc\fP
in the Diagnostics section of the generated Xcode scheme.
.sp
This property is initialized by the value of the variable
\fI\%CMAKE_XCODE_SCHEME_GUARD_MALLOC\fP if it is set
when a target is created.
.sp
Please refer to the \fI\%XCODE_GENERATE_SCHEME\fP target property
documentation to see all Xcode schema related properties.
.SS XCODE_SCHEME_LAUNCH_CONFIGURATION
.sp
Added in version 3.25.

.sp
Set the build configuration to run the target.
.sp
This property is initialized by the value of the variable
\fI\%CMAKE_XCODE_SCHEME_LAUNCH_CONFIGURATION\fP
if it is set when a target is created.
.sp
Please refer to the \fI\%XCODE_GENERATE_SCHEME\fP target property
documentation to see all Xcode schema related properties.
.SS XCODE_SCHEME_TEST_CONFIGURATION
.sp
Added in version 4.0.

.sp
Set the build configuration to test the target.
.sp
This property is initialized by the value of the variable
\fI\%CMAKE_XCODE_SCHEME_TEST_CONFIGURATION\fP
if it is set when a target is created.
.sp
Please refer to the \fI\%XCODE_GENERATE_SCHEME\fP target property
documentation to see all Xcode schema related properties.
.SS XCODE_SCHEME_LAUNCH_MODE
.sp
Added in version 3.25.

.sp
Property value for \fBLaunch\fP in the Info section of the generated Xcode
scheme.
.sp
Possible values are:
.INDENT 0.0
.TP
.B \fBAUTO\fP
Launch automatically. This is the default.
.TP
.B \fBWAIT\fP
Wait for the executable to be launched.
.UNINDENT
.sp
This property is initialized by the value of the variable
\fI\%CMAKE_XCODE_SCHEME_LAUNCH_MODE\fP if it is set when a target is
created.
.sp
Please refer to the \fI\%XCODE_GENERATE_SCHEME\fP target property
documentation to see all Xcode schema related properties.
.SS XCODE_SCHEME_LLDB_INIT_FILE
.sp
Added in version 4.0.

.sp
Property value for \fBLLDB Init File\fP in the Info section of the
generated Xcode scheme. In case the value contains generator
expressions those are evaluated.
.sp
This property is initialized by the value of the variable
\fI\%CMAKE_XCODE_SCHEME_LLDB_INIT_FILE\fP if it is set
when a target is created.
.sp
Please refer to the \fI\%XCODE_GENERATE_SCHEME\fP target property
documentation to see all Xcode schema related properties.
.SS XCODE_SCHEME_MAIN_THREAD_CHECKER_STOP
.sp
Added in version 3.13.

.sp
Whether to enable the \fBMain Thread Checker\fP option
\fBPause on issues\fP
in the Diagnostics section of the generated Xcode scheme.
.sp
This property is initialized by the value of the variable
\fI\%CMAKE_XCODE_SCHEME_MAIN_THREAD_CHECKER_STOP\fP if it is set
when a target is created.
.sp
Please refer to the \fI\%XCODE_GENERATE_SCHEME\fP target property
documentation to see all Xcode schema related properties.
.SS XCODE_SCHEME_MALLOC_GUARD_EDGES
.sp
Added in version 3.13.

.sp
Whether to enable \fBMalloc Guard Edges\fP
in the Diagnostics section of the generated Xcode scheme.
.sp
This property is initialized by the value of the variable
\fI\%CMAKE_XCODE_SCHEME_MALLOC_GUARD_EDGES\fP if it is set
when a target is created.
.sp
Please refer to the \fI\%XCODE_GENERATE_SCHEME\fP target property
documentation to see all Xcode schema related properties.
.SS XCODE_SCHEME_MALLOC_SCRIBBLE
.sp
Added in version 3.13.

.sp
Whether to enable \fBMalloc Scribble\fP
in the Diagnostics section of the generated Xcode scheme.
.sp
This property is initialized by the value of the variable
\fI\%CMAKE_XCODE_SCHEME_MALLOC_SCRIBBLE\fP if it is set
when a target is created.
.sp
Please refer to the \fI\%XCODE_GENERATE_SCHEME\fP target property
documentation to see all Xcode schema related properties.
.SS XCODE_SCHEME_MALLOC_STACK
.sp
Added in version 3.13.

.sp
Whether to enable \fBMalloc Stack\fP in the Diagnostics
section of the generated Xcode scheme.
.sp
This property is initialized by the value of the variable
\fI\%CMAKE_XCODE_SCHEME_MALLOC_STACK\fP if it is set
when a target is created.
.sp
Please refer to the \fI\%XCODE_GENERATE_SCHEME\fP target property
documentation to see all Xcode schema related properties.
.SS XCODE_SCHEME_THREAD_SANITIZER
.sp
Added in version 3.13.

.sp
Whether to enable \fBThread Sanitizer\fP in the Diagnostics
section of the generated Xcode scheme.
.sp
This property is initialized by the value of the variable
\fI\%CMAKE_XCODE_SCHEME_THREAD_SANITIZER\fP if it is set
when a target is created.
.sp
Please refer to the \fI\%XCODE_GENERATE_SCHEME\fP target property
documentation to see all Xcode schema related properties.
.SS XCODE_SCHEME_THREAD_SANITIZER_STOP
.sp
Added in version 3.13.

.sp
Whether to enable \fBThread Sanitizer \- Pause on issues\fP
in the Diagnostics section of the generated Xcode scheme.
.sp
This property is initialized by the value of the variable
\fI\%CMAKE_XCODE_SCHEME_THREAD_SANITIZER_STOP\fP if it is set
when a target is created.
.sp
Please refer to the \fI\%XCODE_GENERATE_SCHEME\fP target property
documentation to see all Xcode schema related properties.
.SS XCODE_SCHEME_UNDEFINED_BEHAVIOUR_SANITIZER
.sp
Added in version 3.13.

.sp
Whether to enable \fBUndefined Behavior Sanitizer\fP
in the Diagnostics section of the generated Xcode scheme.
.sp
This property is initialized by the value of the variable
\fI\%CMAKE_XCODE_SCHEME_UNDEFINED_BEHAVIOUR_SANITIZER\fP
if it is set when a target is created.
.sp
Please refer to the \fI\%XCODE_GENERATE_SCHEME\fP target property
documentation to see all Xcode schema related properties.
.SS XCODE_SCHEME_UNDEFINED_BEHAVIOUR_SANITIZER_STOP
.sp
Added in version 3.13.

.sp
Whether to enable \fBUndefined Behavior Sanitizer\fP option
\fBPause on issues\fP
in the Diagnostics section of the generated Xcode scheme.
.sp
This property is initialized by the value of the variable
\fI\%CMAKE_XCODE_SCHEME_UNDEFINED_BEHAVIOUR_SANITIZER_STOP\fP
if it is set when a target is created.
.sp
Please refer to the \fI\%XCODE_GENERATE_SCHEME\fP target property
documentation to see all Xcode schema related properties.
.SS XCODE_SCHEME_WORKING_DIRECTORY
.sp
Added in version 3.17.

.sp
Specify the \fBWorking Directory\fP of the \fIRun\fP and \fIProfile\fP
actions in the generated Xcode scheme. In case the value contains
generator expressions those are evaluated.
.sp
This property is initialized by the value of the variable
\fI\%CMAKE_XCODE_SCHEME_WORKING_DIRECTORY\fP if it is set
when a target is created.
.sp
Please refer to the \fI\%XCODE_GENERATE_SCHEME\fP target property
documentation to see all Xcode schema related properties.
.sp
See also \fI\%DEBUGGER_WORKING_DIRECTORY\fP\&.
.SS XCODE_SCHEME_ZOMBIE_OBJECTS
.sp
Added in version 3.13.

.sp
Whether to enable \fBZombie Objects\fP
in the Diagnostics section of the generated Xcode scheme.
.sp
This property is initialized by the value of the variable
\fI\%CMAKE_XCODE_SCHEME_ZOMBIE_OBJECTS\fP if it is set
when a target is created.
.sp
Please refer to the \fI\%XCODE_GENERATE_SCHEME\fP target property
documentation to see all Xcode schema related properties.
.SS XCODE_XCCONFIG
.sp
Added in version 3.24.

.sp
If set, the \fI\%Xcode\fP generator will register the specified
file as a target\-level XCConfig file. For global XCConfig files see
the \fI\%CMAKE_XCODE_XCCONFIG\fP variable.
.sp
This feature is intended to ease migration from native Xcode projects
to CMake projects.
.sp
Contents of \fBXCODE_XCCONFIG\fP may use
\fI\%generator expressions\fP\&.
.SS XCTEST
.sp
Added in version 3.3.

.sp
Boolean target property that indicates whether a target is an XCTest CFBundle
(Core Foundation Bundle) on Apple systems.
.sp
This property is usually set automatically by the \fI\%xctest_add_bundle()\fP
command provided by the \fI\%FindXCTest\fP module.
.sp
If a module library target has this property set to boolean true, it will be
built as a CFBundle when built on Apple system, with the required CFBundle
directory structure.
.sp
This property depends on \fI\%BUNDLE\fP target property to be effective.
.SH PROPERTIES ON TESTS
.SS ATTACHED_FILES
.sp
Attach a list of files to a dashboard submission.
.sp
Set this property to a list of files that will be encoded and
submitted to the dashboard as an addition to the test result.
.SS ATTACHED_FILES_ON_FAIL
.sp
Attach a list of files to a dashboard submission if the test fails.
.sp
Same as \fI\%ATTACHED_FILES\fP, but these files will only be
included if the test does not pass.
.SS COST
.sp
This property describes the cost of a test.  When parallel testing is
enabled, tests in the test set will be run in descending order of cost.
Projects can explicitly define the cost of a test by setting this property
to a floating point value.
.sp
When the cost of a test is not defined by the project,
\fI\%ctest\fP will initially use a default cost of \fB0\fP\&.
It computes a weighted average of the cost each time a test is run and
uses that as an improved estimate of the cost for the next run.  The more
a test is re\-run in the same build directory, the more representative the
cost should become.
.SS DEPENDS
.sp
Specifies that this test should only be run after the specified list of tests.
.sp
Set this to a list of tests that must finish before this test is run. The
results of those tests are not considered, the dependency relationship is
purely for order of execution (i.e. it is really just a \fIrun after\fP
relationship). Consider using test fixtures with setup tests if a dependency
with successful completion is required (see \fI\%FIXTURES_REQUIRED\fP).
.SS Examples
.INDENT 0.0
.INDENT 3.5
.sp
.EX
add_test(NAME baseTest1 ...)
add_test(NAME baseTest2 ...)
add_test(NAME dependsTest12 ...)

set_tests_properties(dependsTest12 PROPERTIES DEPENDS \(dqbaseTest1;baseTest2\(dq)
# dependsTest12 runs after baseTest1 and baseTest2, even if they fail
.EE
.UNINDENT
.UNINDENT
.SS DISABLED
.sp
Added in version 3.9.

.sp
If set to \fBTrue\fP, the test will be skipped and its status will be \(aqNot Run\(aq. A
\fBDISABLED\fP test will not be counted in the total number of tests and its
completion status will be reported to CDash as \fBDisabled\fP\&.
.sp
A \fBDISABLED\fP test does not participate in test fixture dependency resolution.
If a \fBDISABLED\fP test has fixture requirements defined in its
\fI\%FIXTURES_REQUIRED\fP property, it will not cause setup or cleanup
tests for those fixtures to be added to the test set.
.sp
If a test with the \fI\%FIXTURES_SETUP\fP property set is \fBDISABLED\fP,
the fixture behavior will be as though that setup test was passing and any test
case requiring that fixture will still run.
.SS ENVIRONMENT
.sp
Specify environment variables that should be defined for running a test.
.sp
Set to a \fI\%semicolon\-separated list\fP list
of environment variables and values of the form \fBMYVAR=value\fP\&.
Those environment variables will be defined while running the test.
The environment changes from this property do not affect other tests.
.SS ENVIRONMENT_MODIFICATION
.sp
Added in version 3.22.

.sp
Specify environment variables that should be modified for running a test. Note
that the operations performed by this property are performed after the
\fI\%ENVIRONMENT\fP property is already applied.
.sp
Set to a \fI\%semicolon\-separated list\fP of
environment variables and values of the form \fBMYVAR=OP:VALUE\fP,
where \fBMYVAR\fP is the case\-sensitive name of an environment variable
to be modified.  Entries are considered in the order specified in the
property\(aqs value.  The \fBOP\fP may be one of:
.INDENT 0.0
.IP \(bu 2
\fBreset\fP: Reset to the unmodified value, ignoring all modifications to
\fBMYVAR\fP prior to this entry. Note that this will reset the variable to
the value set by \fI\%ENVIRONMENT\fP, if it was set, and otherwise
to its state from the rest of the CTest execution.
.IP \(bu 2
\fBset\fP: Replaces the current value of \fBMYVAR\fP with \fBVALUE\fP\&.
.IP \(bu 2
\fBunset\fP: Unsets the current value of \fBMYVAR\fP\&.
.IP \(bu 2
\fBstring_append\fP: Appends singular \fBVALUE\fP to the current value of
\fBMYVAR\fP\&.
.IP \(bu 2
\fBstring_prepend\fP: Prepends singular \fBVALUE\fP to the current value of
\fBMYVAR\fP\&.
.IP \(bu 2
\fBpath_list_append\fP: Appends singular \fBVALUE\fP to the current value of
\fBMYVAR\fP using the host platform\(aqs path list separator (\fB;\fP on Windows
and \fB:\fP elsewhere).
.IP \(bu 2
\fBpath_list_prepend\fP: Prepends singular \fBVALUE\fP to the current value of
\fBMYVAR\fP using the host platform\(aqs path list separator (\fB;\fP on Windows
and \fB:\fP elsewhere).
.IP \(bu 2
\fBcmake_list_append\fP: Appends singular \fBVALUE\fP to the current value of
\fBMYVAR\fP using \fB;\fP as the separator.
.IP \(bu 2
\fBcmake_list_prepend\fP: Prepends singular \fBVALUE\fP to the current value of
\fBMYVAR\fP using \fB;\fP as the separator.
.UNINDENT
.sp
Unrecognized \fBOP\fP values will result in the test failing before it is
executed. This is so that future operations may be added without changing
valid behavior of existing tests.
.sp
The environment changes from this property do not affect other tests.
.SS FAIL_REGULAR_EXPRESSION
.sp
If the test output (stdout or stderr) matches this regular expression the test
will fail, regardless of the process exit code. Tests that exceed the timeout
specified by \fI\%TIMEOUT\fP fail regardless of
\fBFAIL_REGULAR_EXPRESSION\fP\&. Any non\-zero return code or system\-level test
failures including segmentation faults, signal abort, or heap errors fail the
test even if the regular expression does not match.
.sp
If set, if the output matches one of specified regular expressions, the test
will fail.  Example:
.INDENT 0.0
.INDENT 3.5
.sp
.EX
# test would pass, except for FAIL_REGULAR_EXPRESSION
add_test(NAME mytest COMMAND ${CMAKE_COMMAND} \-E echo \(dqFailed\(dq)

set_property(TEST mytest PROPERTY
  FAIL_REGULAR_EXPRESSION \(dq[^a\-z]Error;ERROR;Failed\(dq
)
.EE
.UNINDENT
.UNINDENT
.sp
\fBFAIL_REGULAR_EXPRESSION\fP expects a list of regular expressions.
.sp
See also the \fI\%PASS_REGULAR_EXPRESSION\fP and
\fI\%SKIP_REGULAR_EXPRESSION\fP test properties.
.SS FIXTURES_CLEANUP
.sp
Added in version 3.7.

.sp
Specifies a list of fixtures for which the test is to be treated as a cleanup
test. These fixture names are distinct from test case names and are not
required to have any similarity to the names of tests associated with them.
.sp
Fixture cleanup tests are ordinary tests with all of the usual test
functionality. Setting the \fBFIXTURES_CLEANUP\fP property for a test has two
primary effects:
.INDENT 0.0
.IP \(bu 2
CTest will ensure the test executes after all other tests which list any of
the fixtures in its \fI\%FIXTURES_REQUIRED\fP property.
.IP \(bu 2
If CTest is asked to run only a subset of tests (e.g. using regular
expressions or the \fB\-\-rerun\-failed\fP option) and the cleanup test is not in
the set of tests to run, it will automatically be added if any tests in the
set require any fixture listed in \fBFIXTURES_CLEANUP\fP\&.
.UNINDENT
.sp
A cleanup test can have multiple fixtures listed in its \fBFIXTURES_CLEANUP\fP
property. It will execute only once for the whole CTest run, not once for each
fixture. A fixture can also have more than one cleanup test defined. If there
are multiple cleanup tests for a fixture, projects can control their order with
the usual \fI\%DEPENDS\fP test property if necessary.
.sp
A cleanup test is allowed to require other fixtures, but not any fixture listed
in its \fBFIXTURES_CLEANUP\fP property. For example:
.INDENT 0.0
.INDENT 3.5
.sp
.EX
# Ok: Dependent fixture is different to cleanup
set_tests_properties(cleanupFoo PROPERTIES
  FIXTURES_CLEANUP  Foo
  FIXTURES_REQUIRED Bar
)

# Error: cannot require same fixture as cleanup
set_tests_properties(cleanupFoo PROPERTIES
  FIXTURES_CLEANUP  Foo
  FIXTURES_REQUIRED Foo
)
.EE
.UNINDENT
.UNINDENT
.sp
Cleanup tests will execute even if setup or regular tests for that fixture fail
or are skipped.
.sp
See \fI\%FIXTURES_REQUIRED\fP for a more complete discussion of how to use
test fixtures.
.SS FIXTURES_REQUIRED
.sp
Added in version 3.7.

.sp
Specifies a list of fixtures the test requires. Fixture names are case
sensitive and they are not required to have any similarity to test names.
.sp
Fixtures are a way to attach setup and cleanup tasks to a set of tests. If a
test requires a given fixture, then all tests marked as setup tasks for that
fixture will be executed first (once for the whole set of tests, not once per
test requiring the fixture). After all tests requiring a particular fixture
have completed, CTest will ensure all tests marked as cleanup tasks for that
fixture are then executed. Tests are marked as setup tasks with the
\fI\%FIXTURES_SETUP\fP property and as cleanup tasks with the
\fI\%FIXTURES_CLEANUP\fP property. If any of a fixture\(aqs setup tests fail,
all tests listing that fixture in their \fBFIXTURES_REQUIRED\fP property will not
be executed. The cleanup tests for the fixture will always be executed, even if
some setup tests fail.
.sp
When CTest is asked to execute only a subset of tests (e.g. by the use of
regular expressions or when run with the \fI\%\-\-rerun\-failed\fP
command line option), it will automatically add any setup or cleanup tests for
fixtures required by any of the tests that are in the execution set. This
behavior can be overridden with the \fI\%\-FS\fP,
\fI\%\-FC\fP and \fI\%\-FA\fP command line options to
\fI\%ctest(1)\fP if desired.
.sp
Since setup and cleanup tasks are also tests, they can have an ordering
specified by the \fI\%DEPENDS\fP test property just like any other tests.
This can be exploited to implement setup or cleanup using multiple tests for a
single fixture to modularise setup or cleanup logic.
.sp
The concept of a fixture is different to that of a resource specified by
\fI\%RESOURCE_LOCK\fP, but they may be used together. A fixture defines a
set of tests which share setup and cleanup requirements, whereas a resource
lock has the effect of ensuring a particular set of tests do not run in
parallel. Some situations may need both, such as setting up a database,
serializing test access to that database and deleting the database again at the
end. For such cases, tests would populate both \fBFIXTURES_REQUIRED\fP and
\fI\%RESOURCE_LOCK\fP to combine the two behaviors. Names used for
\fI\%RESOURCE_LOCK\fP have no relationship with names of fixtures, so note
that a resource lock does not imply a fixture and vice versa.
.sp
Consider the following example which represents a database test scenario
similar to that mentioned above:
.INDENT 0.0
.INDENT 3.5
.sp
.EX
add_test(NAME testsDone   COMMAND emailResults)
add_test(NAME fooOnly     COMMAND testFoo)
add_test(NAME dbOnly      COMMAND testDb)
add_test(NAME dbWithFoo   COMMAND testDbWithFoo)
add_test(NAME createDB    COMMAND initDB)
add_test(NAME setupUsers  COMMAND userCreation)
add_test(NAME cleanupDB   COMMAND deleteDB)
add_test(NAME cleanupFoo  COMMAND removeFoos)

set_tests_properties(setupUsers PROPERTIES DEPENDS createDB)

set_tests_properties(createDB   PROPERTIES FIXTURES_SETUP    DB)
set_tests_properties(setupUsers PROPERTIES FIXTURES_SETUP    DB)
set_tests_properties(cleanupDB  PROPERTIES FIXTURES_CLEANUP  DB)
set_tests_properties(cleanupFoo PROPERTIES FIXTURES_CLEANUP  Foo)
set_tests_properties(testsDone  PROPERTIES FIXTURES_CLEANUP  \(dqDB;Foo\(dq)

set_tests_properties(fooOnly    PROPERTIES FIXTURES_REQUIRED Foo)
set_tests_properties(dbOnly     PROPERTIES FIXTURES_REQUIRED DB)
set_tests_properties(dbWithFoo  PROPERTIES FIXTURES_REQUIRED \(dqDB;Foo\(dq)

set_tests_properties(dbOnly dbWithFoo createDB setupUsers cleanupDB
                     PROPERTIES RESOURCE_LOCK DbAccess)
.EE
.UNINDENT
.UNINDENT
.sp
Key points from this example:
.INDENT 0.0
.IP \(bu 2
Two fixtures are defined: \fBDB\fP and \fBFoo\fP\&. Tests can require a single
fixture as \fBfooOnly\fP and \fBdbOnly\fP do, or they can depend on multiple
fixtures like \fBdbWithFoo\fP does.
.IP \(bu 2
A \fBDEPENDS\fP relationship is set up to ensure \fBsetupUsers\fP happens after
\fBcreateDB\fP, both of which are setup tests for the \fBDB\fP fixture and will
therefore be executed before the \fBdbOnly\fP and \fBdbWithFoo\fP tests
automatically.
.IP \(bu 2
No explicit \fBDEPENDS\fP relationships were needed to make the setup tests run
before or the cleanup tests run after the regular tests.
.IP \(bu 2
The \fBFoo\fP fixture has no setup tests defined, only a single cleanup test.
.IP \(bu 2
\fBtestsDone\fP is a cleanup test for both the \fBDB\fP and \fBFoo\fP fixtures.
Therefore, it will only execute once regular tests for both fixtures have
finished (i.e. after \fBfooOnly\fP, \fBdbOnly\fP and \fBdbWithFoo\fP). No
\fBDEPENDS\fP relationship was specified for \fBtestsDone\fP, so it is free to
run before, after or concurrently with other cleanup tests for either
fixture.
.IP \(bu 2
The setup and cleanup tests never list the fixtures they are for in their own
\fBFIXTURES_REQUIRED\fP property, as that would result in a dependency on
themselves and be considered an error.
.UNINDENT
.SS FIXTURES_SETUP
.sp
Added in version 3.7.

.sp
Specifies a list of fixtures for which the test is to be treated as a setup
test. These fixture names are distinct from test case names and are not
required to have any similarity to the names of tests associated with them.
.sp
Fixture setup tests are ordinary tests with all of the usual test
functionality. Setting the \fBFIXTURES_SETUP\fP property for a test has two
primary effects:
.INDENT 0.0
.IP \(bu 2
CTest will ensure the test executes before any other test which lists the
fixture name(s) in its \fI\%FIXTURES_REQUIRED\fP property.
.IP \(bu 2
If CTest is asked to run only a subset of tests (e.g. using regular
expressions or the \fB\-\-rerun\-failed\fP option) and the setup test is not in
the set of tests to run, it will automatically be added if any tests in the
set require any fixture listed in \fBFIXTURES_SETUP\fP\&.
.UNINDENT
.sp
A setup test can have multiple fixtures listed in its \fBFIXTURES_SETUP\fP
property. It will execute only once for the whole CTest run, not once for each
fixture. A fixture can also have more than one setup test defined. If there are
multiple setup tests for a fixture, projects can control their order with the
usual \fI\%DEPENDS\fP test property if necessary.
.sp
A setup test is allowed to require other fixtures, but not any fixture listed
in its \fBFIXTURES_SETUP\fP property. For example:
.INDENT 0.0
.INDENT 3.5
.sp
.EX
# Ok: dependent fixture is different to setup
set_tests_properties(setupFoo PROPERTIES
  FIXTURES_SETUP    Foo
  FIXTURES_REQUIRED Bar
)

# Error: cannot require same fixture as setup
set_tests_properties(setupFoo PROPERTIES
  FIXTURES_SETUP    Foo
  FIXTURES_REQUIRED Foo
)
.EE
.UNINDENT
.UNINDENT
.sp
If any of a fixture\(aqs setup tests fail, none of the tests listing that fixture
in its \fI\%FIXTURES_REQUIRED\fP property will be run. Cleanup tests will,
however, still be executed.
.sp
See \fI\%FIXTURES_REQUIRED\fP for a more complete discussion of how to use
test fixtures.
.SS GENERATED_RESOURCE_SPEC_FILE
.sp
Added in version 3.28.

.sp
Path to the \fI\%dynamically\-generated resource spec file\fP generated by this test.
.SS LABELS
.sp
Specify a list of text labels associated with a test.  The labels are
reported in both the \fBctest\fP output summary and in dashboard submissions.
They can also be used to filter the set of tests to be executed (see the
\fI\%ctest \-L\fP and \fI\%ctest \-LE\fP options).
.sp
See \fI\%Additional Labels\fP for adding labels to a test dynamically during
test execution.
.SS MEASUREMENT
.sp
Specify a \fBCDASH\fP measurement and value to be reported for a test.
.sp
If set to a name then that name will be reported to \fBCDASH\fP as a named
measurement with a value of \fB1\fP\&.  You may also specify a value by
setting \fBMEASUREMENT\fP to \fBmeasurement=value\fP\&.
.SS PASS_REGULAR_EXPRESSION
.sp
The test output (stdout or stderr) must match this regular expression
for the test to pass. The process exit code is ignored. Tests that exceed
the timeout specified by \fI\%TIMEOUT\fP still fail regardless of
\fBPASS_REGULAR_EXPRESSION\fP\&. System\-level test failures including
segmentation faults, signal abort, or heap errors may fail the test even
if \fBPASS_REGULAR_EXPRESSION\fP is matched.
.sp
Example:
.INDENT 0.0
.INDENT 3.5
.sp
.EX
add_test(NAME mytest COMMAND ${CMAKE_COMMAND} \-E echo \(dqPassed this test\(dq)

set_property(TEST mytest PROPERTY
  PASS_REGULAR_EXPRESSION \(dqpass;Passed\(dq
)
.EE
.UNINDENT
.UNINDENT
.sp
\fBPASS_REGULAR_EXPRESSION\fP expects a list of regular expressions.
.sp
To run a test that may have a system\-level failure, but still pass if
\fBPASS_REGULAR_EXPRESSION\fP matches, use a CMake command to wrap the
executable run. Note that this will prevent automatic handling of the
\fI\%CROSSCOMPILING_EMULATOR\fP and \fI\%TEST_LAUNCHER\fP
target property.
.INDENT 0.0
.INDENT 3.5
.sp
.EX
add_executable(main main.c)

add_test(NAME sigabrt COMMAND ${CMAKE_COMMAND} \-E env $<TARGET_FILE:main>)

set_property(TEST sigabrt PROPERTY PROPERTY_REGULAR_EXPRESSION \(dqpass;Passed\(dq)
.EE
.UNINDENT
.UNINDENT
.INDENT 0.0
.INDENT 3.5
.sp
.EX
#include <signal.h>
#include <stdio.h>

int main(void){
    fprintf(stdout, \(dqPassed\en\(dq);
    fflush(stdout);  /* ensure the output buffer is seen */
    raise(SIGABRT);
    return 0;
}
.EE
.UNINDENT
.UNINDENT
.sp
See also the \fI\%FAIL_REGULAR_EXPRESSION\fP and
\fI\%SKIP_REGULAR_EXPRESSION\fP test properties.
.SS PROCESSOR_AFFINITY
.sp
Added in version 3.12.

.sp
Set to a true value to ask CTest to launch the test process with CPU affinity
for a fixed set of processors.  If enabled and supported for the current
platform, CTest will choose a set of processors to place in the CPU affinity
mask when launching the test process.  The number of processors in the set is
determined by the \fI\%PROCESSORS\fP test property or the number of
processors available to CTest, whichever is smaller.  The set of processors
chosen will be disjoint from the processors assigned to other concurrently
running tests that also have the \fBPROCESSOR_AFFINITY\fP property enabled.
.SS PROCESSORS
.sp
Set to specify how many process slots this test requires.
If not set, the default is \fB1\fP processor.
.sp
Denotes the number of processors that this test will require.  This is
typically used for MPI tests, and should be used in conjunction with
the \fI\%ctest_test()\fP \fBPARALLEL_LEVEL\fP option.
.sp
This will also be used to display a weighted test timing result in label and
subproject summaries in the command line output of \fI\%ctest(1)\fP\&. The wall
clock time for the test run will be multiplied by this property to give a
better idea of how much cpu resource CTest allocated for the test.
.sp
See also the \fI\%PROCESSOR_AFFINITY\fP test property.
.SS REQUIRED_FILES
.sp
List of files required to run the test.  The filenames are relative to the
test \fI\%WORKING_DIRECTORY\fP unless an absolute path is specified.
.sp
If set to a list of files, the test will not be run unless all of the
files exist.
.SS Examples
.sp
Suppose that \fBtest.txt\fP is created by test \fBbaseTest\fP and \fBnone.txt\fP
does not exist:
.INDENT 0.0
.INDENT 3.5
.sp
.EX
add_test(NAME baseTest ...)   # Assumed to create test.txt
add_test(NAME fileTest ...)

# The following ensures that if baseTest is successful, test.txt will
# have been created before fileTest is run
set_tests_properties(fileTest PROPERTIES
  DEPENDS baseTest
  REQUIRED_FILES test.txt
)

add_test(NAME notRunTest ...)

# The following makes notRunTest depend on two files. Nothing creates
# the none.txt file, so notRunTest will fail with status \(dqNot Run\(dq.
set_tests_properties(notRunTest PROPERTIES
  REQUIRED_FILES \(dqtest.txt;none.txt\(dq
)
.EE
.UNINDENT
.UNINDENT
.sp
The above example demonstrates how \fBREQUIRED_FILES\fP works, but it is not the
most robust way to implement test ordering with failure detection.  For that,
test fixtures are a better alternative (see \fI\%FIXTURES_REQUIRED\fP).
.SS RESOURCE_GROUPS
.sp
Added in version 3.16.

.sp
Specify resources required by a test, grouped in a way that is meaningful to
the test.  See \fI\%resource allocation\fP
for more information on how this property integrates into the CTest resource
allocation feature.
.sp
The \fBRESOURCE_GROUPS\fP property is a \fI\%semicolon\-separated list\fP of group descriptions. Each entry consists of an optional
number of groups using the description followed by a series of resource
requirements for those groups. These requirements (and the number of groups)
are separated by commas. The resource requirements consist of the name of a
resource type, followed by a colon, followed by an unsigned integer
specifying the number of slots required on one resource of the given type.
.sp
The \fBRESOURCE_GROUPS\fP property tells CTest what resources a test expects
to use grouped in a way meaningful to the test.  The test itself must read
the \fI\%environment variables\fP to
determine which resources have been allocated to each group.  For example,
each group may correspond to a process the test will spawn when executed.
.sp
Consider the following example:
.INDENT 0.0
.INDENT 3.5
.sp
.EX
add_test(NAME MyTest COMMAND MyExe)
set_property(TEST MyTest PROPERTY RESOURCE_GROUPS
  \(dq2,gpus:2\(dq
  \(dqgpus:4,crypto_chips:2\(dq)
.EE
.UNINDENT
.UNINDENT
.sp
In this example, there are two group descriptions (implicitly separated by a
semicolon.) The content of the first description is \fB2,gpus:2\fP\&. This
description specifies 2 groups, each of which requires 2 slots from a single
GPU. The content of the second description is \fBgpus:4,crypto_chips:2\fP\&. This
description does not specify a group count, so a default of 1 is assumed.
This single group requires 4 slots from a single GPU and 2 slots from a
single cryptography chip. In total, 3 resource groups are specified for this
test, each with its own unique requirements.
.sp
Note that the number of slots following the resource type specifies slots from
a \fIsingle\fP instance of the resource. If the resource group can tolerate
receiving slots from different instances of the same resource, it can indicate
this by splitting the specification into multiple requirements of one slot. For
example:
.INDENT 0.0
.INDENT 3.5
.sp
.EX
add_test(NAME MyTest COMMAND MyExe)
set_property(TEST MyTest PROPERTY RESOURCE_GROUPS
  \(dqgpus:1,gpus:1,gpus:1,gpus:1\(dq)
.EE
.UNINDENT
.UNINDENT
.sp
In this case, the single resource group indicates that it needs four GPU slots,
all of which may come from separate GPUs (though they don\(aqt have to; CTest may
still assign slots from the same GPU.)
.sp
When CTest sets the \fI\%environment variables\fP for a test, it assigns a group number
based on the group description, starting at 0 on the left and the number of
groups minus 1 on the right. For example, in the example above, the two
groups in the first description would have IDs of 0 and 1, and the single
group in the second description would have an ID of 2.
.sp
Both the \fBRESOURCE_GROUPS\fP and \fI\%RESOURCE_LOCK\fP properties serve
similar purposes, but they are distinct and orthogonal. Resources specified by
\fBRESOURCE_GROUPS\fP do not affect \fI\%RESOURCE_LOCK\fP, and vice versa.
Whereas \fI\%RESOURCE_LOCK\fP is a simpler property that is used for
locking one global resource, \fBRESOURCE_GROUPS\fP is a more advanced property
that allows multiple tests to simultaneously use multiple resources of the
same type, specifying their requirements in a fine\-grained manner.
.SS RESOURCE_LOCK
.sp
Specify a list of resources that are locked by this test.
.sp
If multiple tests specify the same resource lock, they are guaranteed
not to run concurrently.
.sp
See also \fI\%FIXTURES_REQUIRED\fP if the resource requires any setup or
cleanup steps.
.sp
Both the \fI\%RESOURCE_GROUPS\fP and \fBRESOURCE_LOCK\fP properties serve
similar purposes, but they are distinct and orthogonal. Resources specified by
\fI\%RESOURCE_GROUPS\fP do not affect \fBRESOURCE_LOCK\fP, and vice versa.
Whereas \fBRESOURCE_LOCK\fP is a simpler property that is used for locking one
global resource, \fI\%RESOURCE_GROUPS\fP is a more advanced property
that allows multiple tests to simultaneously use multiple resources of the
same type, specifying their requirements in a fine\-grained manner.
.SS RUN_SERIAL
.sp
Do not run this test in parallel with any other test.
.sp
Use this option in conjunction with the ctest_test \fBPARALLEL_LEVEL\fP
option to specify that this test should not be run in parallel with
any other tests.
.SS SKIP_REGULAR_EXPRESSION
.sp
Added in version 3.16.

.sp
If the test output (stderr or stdout) matches this regular expression the test
will be marked as skipped, regardless of the process exit code. Tests that
exceed the timeout specified by \fI\%TIMEOUT\fP still fail regardless of
\fBSKIP_REGULAR_EXPRESSION\fP\&. System\-level test failures including segmentation
faults, signal abort, or heap errors may fail the test even if the regular
expression matches.
.sp
Example:
.INDENT 0.0
.INDENT 3.5
.sp
.EX
add_test(NAME mytest COMMAND ${CMAKE_COMMAND} \-E echo \(dqSkipped this test\(dq)

set_property(TEST mytest PROPERTY
  SKIP_REGULAR_EXPRESSION \(dq[^a\-z]Skip\(dq \(dqSKIP\(dq \(dqSkipped\(dq
)
.EE
.UNINDENT
.UNINDENT
.sp
\fBSKIP_REGULAR_EXPRESSION\fP expects a list of regular expressions.
.sp
To run a test that may have a system\-level failure, but still skip if
\fBSKIP_REGULAR_EXPRESSION\fP matches, use a CMake command to wrap the
executable run. Note that this will prevent automatic handling of the
\fI\%CROSSCOMPILING_EMULATOR\fP and \fI\%TEST_LAUNCHER\fP
target property.
.INDENT 0.0
.INDENT 3.5
.sp
.EX
add_executable(main main.c)

add_test(NAME sigabrt COMMAND ${CMAKE_COMMAND} \-E env $<TARGET_FILE:main>)

set_property(TEST sigabrt PROPERTY SKIP_REGULAR_EXPRESSION \(dqSIGABRT;[aA]bort\(dq)
.EE
.UNINDENT
.UNINDENT
.INDENT 0.0
.INDENT 3.5
.sp
.EX
#include <signal.h>

int main(void){ raise(SIGABRT); return 0; }
.EE
.UNINDENT
.UNINDENT
.sp
See also the \fI\%SKIP_RETURN_CODE\fP,
\fI\%PASS_REGULAR_EXPRESSION\fP, and \fI\%FAIL_REGULAR_EXPRESSION\fP
test properties.
.SS SKIP_RETURN_CODE
.sp
Return code to mark a test as skipped.
.sp
Sometimes only a test itself can determine if all requirements for the
test are met. If such a situation should not be considered a hard failure
a return code of the process can be specified that will mark the test as
\fBNot Run\fP if it is encountered. Valid values are in the range of
0 to 255, inclusive.
.sp
Tests that exceed the timeout specified by \fI\%TIMEOUT\fP still fail
regardless of \fBSKIP_RETURN_CODE\fP\&.
System\-level test failures including segmentation faults,
signal abort, or heap errors may fail the test even if the return code matches.
.INDENT 0.0
.INDENT 3.5
.sp
.EX
# cmake (1) defines this to return code 1
add_test(NAME r1 COMMAND ${CMAKE_COMMAND} \-E false)

set_tests_properties(r1 PROPERTIES SKIP_RETURN_CODE 1)
.EE
.UNINDENT
.UNINDENT
.sp
To run a test that may have a system\-level failure, but still skip if
\fBSKIP_RETURN_CODE\fP matches, use a CMake command to wrap the executable run.
Note that this will prevent automatic handling of the
\fI\%CROSSCOMPILING_EMULATOR\fP and \fI\%TEST_LAUNCHER\fP target
property.
.INDENT 0.0
.INDENT 3.5
.sp
.EX
add_executable(main main.c)

# cmake \-E env <command> returns 1 if the command fails in any way
add_test(NAME sigabrt COMMAND ${CMAKE_COMMAND} \-E env $<TARGET_FILE:main>)

set_property(TEST sigabrt PROPERTY SKIP_RETURN_CODE 1)
.EE
.UNINDENT
.UNINDENT
.INDENT 0.0
.INDENT 3.5
.sp
.EX
#include <signal.h>

int main(void){ raise(SIGABRT); return 0; }
.EE
.UNINDENT
.UNINDENT
.sp
To handle multiple types of cases that may need to be skipped, consider the
\fI\%SKIP_REGULAR_EXPRESSION\fP property.
.SS TIMEOUT
.sp
How many seconds to allow for this test.
.sp
This property if set will limit a test to not take more than the
specified number of seconds to run.  If it exceeds that the test
process will be killed and ctest will move to the next test.  This
setting takes precedence over \fI\%CTEST_TEST_TIMEOUT\fP\&.
.sp
An explicit \fB0\fP value means the test has no timeout, except as
necessary to honor \fI\%ctest \-\-stop\-time\fP\&.
.sp
See also \fI\%TIMEOUT_AFTER_MATCH\fP and
\fI\%TIMEOUT_SIGNAL_NAME\fP\&.
.SS TIMEOUT_AFTER_MATCH
.sp
Added in version 3.6.

.sp
Change a test\(aqs timeout duration after a matching line is encountered
in its output.
.SS Usage
.INDENT 0.0
.INDENT 3.5
.sp
.EX
add_test(mytest ...)
set_property(TEST mytest PROPERTY TIMEOUT_AFTER_MATCH \(dq${seconds}\(dq \(dq${regex}\(dq)
.EE
.UNINDENT
.UNINDENT
.SS Description
.sp
Allow a test \fBseconds\fP to complete after \fBregex\fP is encountered in
its output.
.sp
When the test outputs a line that matches \fBregex\fP its start time is
reset to the current time and its timeout duration is changed to
\fBseconds\fP\&.  Prior to this, the timeout duration is determined by the
\fI\%TIMEOUT\fP property or the \fI\%CTEST_TEST_TIMEOUT\fP
variable if either of these are set.  Because the test\(aqs start time is
reset, its execution time will not include any time that was spent
waiting for the matching output.
.sp
\fBTIMEOUT_AFTER_MATCH\fP is useful for avoiding spurious
timeouts when your test must wait for some system resource to become
available before it can execute.  Set \fI\%TIMEOUT\fP to a longer
duration that accounts for resource acquisition and use
\fBTIMEOUT_AFTER_MATCH\fP to control how long the actual test
is allowed to run.
.sp
If the required resource can be controlled by CTest you should use
\fI\%RESOURCE_LOCK\fP instead of \fBTIMEOUT_AFTER_MATCH\fP\&.
This property should be used when only the test itself can determine
when its required resources are available.
.sp
See also \fI\%TIMEOUT_SIGNAL_NAME\fP\&.
.SS TIMEOUT_SIGNAL_GRACE_PERIOD
.sp
Added in version 3.27.

.sp
If the \fI\%TIMEOUT_SIGNAL_NAME\fP test property is set, this property
specifies the number of seconds to wait for a test process to terminate after
sending the custom signal.  Otherwise, this property has no meaning.
.sp
The grace period may be any real value greater than \fB0.0\fP, but not greater
than \fB60.0\fP\&.  If this property is not set, the default is \fB1.0\fP second.
.sp
This is available only on platforms supporting POSIX signals.
It is not available on Windows.
.SS TIMEOUT_SIGNAL_NAME
.sp
Added in version 3.27.

.sp
Specify a custom signal to send to a test process when its timeout is reached.
This is available only on platforms supporting POSIX signals.
It is not available on Windows.
.sp
The name must be one of the following:
.INDENT 0.0
.INDENT 3.5
.INDENT 0.0
.TP
.B \fBSIGINT\fP
Interrupt.
.TP
.B \fBSIGQUIT\fP
Quit.
.TP
.B \fBSIGTERM\fP
Terminate.
.TP
.B \fBSIGUSR1\fP
User defined signal 1.
.TP
.B \fBSIGUSR2\fP
User defined signal 2.
.UNINDENT
.UNINDENT
.UNINDENT
.sp
The custom signal is sent to the test process to give it a chance
to exit gracefully during a grace period:
.INDENT 0.0
.IP \(bu 2
If the test process created any children, it is responsible for
terminating them too.
.IP \(bu 2
The grace period length is determined by the
\fI\%TIMEOUT_SIGNAL_GRACE_PERIOD\fP test property.
.IP \(bu 2
If the test process does not terminate before the grace period ends,
\fI\%ctest(1)\fP will force termination of its entire process tree
via \fBSIGSTOP\fP and \fBSIGKILL\fP\&.
.UNINDENT
.sp
See also \fI\%CTEST_TEST_TIMEOUT\fP,
\fI\%TIMEOUT\fP, and \fI\%TIMEOUT_AFTER_MATCH\fP\&.
.SS WILL_FAIL
.sp
If \fBtrue\fP, inverts the pass / fail test criteria. Tests for which
\fBWILL_FAIL\fP is \fBtrue\fP fail with return code 0 and pass with non\-zero
return code. Tests that exceed the timeout specified by \fI\%TIMEOUT\fP
still fail regardless of \fBWILL_FAIL\fP\&.
System\-level test failures including segmentation faults,
signal abort, or heap errors may fail the test even if \fBWILL_FAIL\fP is true.
.sp
Example of a test that would ordinarily pass, but fails because \fBWILL_FAIL\fP
is \fBtrue\fP:
.INDENT 0.0
.INDENT 3.5
.sp
.EX
add_test(NAME failed COMMAND ${CMAKE_COMMAND} \-E true)
set_property(TEST failed PROPERTY WILL_FAIL true)
.EE
.UNINDENT
.UNINDENT
.sp
To run a test that may have a system\-level failure, but still pass if
\fBWILL_FAIL\fP is set, use a CMake command to wrap the executable run.
Note that this will prevent automatic handling of the
\fI\%CROSSCOMPILING_EMULATOR\fP and \fI\%TEST_LAUNCHER\fP
target property.
.INDENT 0.0
.INDENT 3.5
.sp
.EX
add_executable(main main.c)

add_test(NAME sigabrt COMMAND ${CMAKE_COMMAND} \-E env $<TARGET_FILE:main>)

set_property(TEST sigabrt PROPERTY WILL_FAIL TRUE)
.EE
.UNINDENT
.UNINDENT
.INDENT 0.0
.INDENT 3.5
.sp
.EX
#include <signal.h>

int main(void){ raise(SIGABRT); return 0; }
.EE
.UNINDENT
.UNINDENT
.SS WORKING_DIRECTORY
.sp
The directory from which the test executable will be called.
.sp
If this is not set, the test will be run with the working directory set to the
binary directory associated with where the test was created (i.e. the
\fI\%CMAKE_CURRENT_BINARY_DIR\fP for where \fI\%add_test()\fP was
called).
.SH PROPERTIES ON SOURCE FILES
.SS ABSTRACT
.sp
Is this source file an abstract class.
.sp
A property on a source file that indicates if the source file
represents a class that is abstract.  This only makes sense for
languages that have a notion of an abstract class and it is only used
by some tools that wrap classes into other languages.
.SS AUTORCC_OPTIONS
.sp
Additional options for \fBrcc\fP when using \fI\%AUTORCC\fP
.sp
This property holds additional command line options which will be used when
\fBrcc\fP is executed during the build via \fI\%AUTORCC\fP, i.e. it is equivalent to the
optional \fBOPTIONS\fP argument of the \fI\%qt4_add_resources()\fP macro.
.sp
By default it is empty.
.sp
The options set on the \fB\&.qrc\fP source file may override
\fI\%AUTORCC_OPTIONS\fP set on the target.
.SS EXAMPLE
.INDENT 0.0
.INDENT 3.5
.sp
.EX
# ...
set_property(SOURCE resources.qrc PROPERTY AUTORCC_OPTIONS \(dq\-\-compress;9\(dq)
# ...
.EE
.UNINDENT
.UNINDENT
.SS AUTOUIC_OPTIONS
.sp
Additional options for \fBuic\fP when using \fI\%AUTOUIC\fP
.sp
This property holds additional command line options
which will be used when \fBuic\fP is executed during the build via
\fI\%AUTOUIC\fP, i.e. it is equivalent to the optional \fBOPTIONS\fP
argument of the \fI\%qt4_wrap_ui()\fP macro.
.sp
By default it is empty.
.sp
The options set on the \fB\&.ui\fP source file may override
\fI\%AUTOUIC_OPTIONS\fP set on the target.
.SS EXAMPLE
.INDENT 0.0
.INDENT 3.5
.sp
.EX
# ...
set_property(SOURCE widget.ui PROPERTY AUTOUIC_OPTIONS \(dq\-\-no\-protection\(dq)
# ...
.EE
.UNINDENT
.UNINDENT
.SS COMPILE_DEFINITIONS
.sp
Preprocessor definitions for compiling a source file.
.sp
The \fBCOMPILE_DEFINITIONS\fP property may be set to a semicolon\-separated
list of preprocessor definitions using the syntax \fBVAR\fP or \fBVAR=value\fP\&.
Function\-style definitions are not supported.  CMake will
automatically escape the value correctly for the native build system
(note that CMake language syntax may require escapes to specify some
values).  This property may be set on a per\-configuration basis using
the name \fBCOMPILE_DEFINITIONS_<CONFIG>\fP where \fB<CONFIG>\fP is an upper\-case
name (ex.  \fBCOMPILE_DEFINITIONS_DEBUG\fP).
.sp
CMake will automatically drop some definitions that are not supported
by the native build tool.  \fI\%Xcode\fP does not support per\-configuration
definitions on source files.
.sp
Added in version 3.26: Any leading \fB\-D\fP on an item will be removed.

.sp
Disclaimer: Most native build tools have poor support for escaping
certain values.  CMake has work\-arounds for many cases but some values
may just not be possible to pass correctly.  If a value does not seem
to be escaped correctly, do not attempt to work\-around the problem by
adding escape sequences to the value.  Your work\-around may break in a
future version of CMake that has improved escape support.  Instead
consider defining the macro in a (configured) header file.  Then
report the limitation.  Known limitations include:
.INDENT 0.0
.INDENT 3.5
.TS
box center;
l|l.
T{
\fB#\fP
T}	T{
Broken almost everywhere.
T}
_
T{
\fB;\fP
T}	T{
Broken in VS IDE 7.0 and Borland Makefiles.
T}
_
T{
\fB,\fP
T}	T{
Broken in VS IDE.
T}
_
T{
\fB%\fP
T}	T{
Broken in some cases in NMake.
T}
_
T{
\fB& |\fP
T}	T{
Broken in some cases on MinGW.
T}
_
T{
\fB^ < > \e \(dq\fP
T}	T{
Broken in most Make tools on Windows.
T}
.TE
.UNINDENT
.UNINDENT
.sp
CMake does not reject these values outright because they do work in
some cases.  Use with caution.
.sp
Contents of \fBCOMPILE_DEFINITIONS\fP may use \fI\%cmake\-generator\-expressions(7)\fP
with the syntax \fB$<...>\fP\&.  See the \fI\%cmake\-generator\-expressions(7)\fP
manual for available expressions.  However, \fI\%Xcode\fP
does not support per\-config per\-source settings, so expressions
that depend on the build configuration are not allowed with that
generator.
.sp
Prefer using generator expressions in \fBCOMPILE_DEFINITIONS\fP over the
deprecated \fI\%COMPILE_DEFINITIONS_<CONFIG>\fP property.
.SS COMPILE_FLAGS
.sp
Additional flags to be added when compiling this source file.
.sp
The \fBCOMPILE_FLAGS\fP property, managed as a string, sets additional compiler
flags used that will be added to the list of compile flags when this source
file builds.  The flags will be added after target\-wide flags.
.sp
Use \fI\%COMPILE_DEFINITIONS\fP to pass additional preprocessor definitions.
.sp
Contents of \fBCOMPILE_FLAGS\fP may use \(dqgenerator expressions\(dq
with the syntax \fB$<...>\fP\&.  See the \fI\%cmake\-generator\-expressions(7)\fP
manual for available expressions.  However, \fI\%Xcode\fP
does not support per\-config per\-source settings, so expressions
that depend on the build configuration are not allowed with that
generator.
.sp
\fBNOTE:\fP
.INDENT 0.0
.INDENT 3.5
This property has been superseded by the \fI\%COMPILE_OPTIONS\fP property.
.UNINDENT
.UNINDENT
.SS COMPILE_OPTIONS
.sp
Added in version 3.11.

.sp
List of additional options to pass to the compiler.
.sp
This property holds a \fI\%semicolon\-separated list\fP
of options and will be added to the list of compile flags when this source
file builds.  The options will be added after target\-wide options.
.sp
Contents of \fBCOMPILE_OPTIONS\fP may use \(dqgenerator expressions\(dq with the
syntax \fB$<...>\fP\&.  See the \fI\%cmake\-generator\-expressions(7)\fP manual
for available expressions.  However, \fI\%Xcode\fP
does not support per\-config per\-source settings, so expressions
that depend on the build configuration are not allowed with that
generator.
.sp
Usage example:
.INDENT 0.0
.INDENT 3.5
.sp
.EX
set_source_files_properties(foo.cpp PROPERTIES COMPILE_OPTIONS \(dq\-Wno\-unused\-parameter;\-Wno\-missing\-field\-initializer\(dq)
.EE
.UNINDENT
.UNINDENT
.sp
Related properties:
.INDENT 0.0
.IP \(bu 2
Prefer this property over \fI\%COMPILE_FLAGS\fP\&.
.IP \(bu 2
Use \fI\%COMPILE_DEFINITIONS\fP to pass additional preprocessor definitions.
.IP \(bu 2
Use \fI\%INCLUDE_DIRECTORIES\fP to pass additional include directories.
.UNINDENT
.sp
Related commands:
.INDENT 0.0
.IP \(bu 2
\fI\%add_compile_options()\fP for directory\-wide settings
.IP \(bu 2
\fI\%target_compile_options()\fP for target\-specific settings
.UNINDENT
.SS CXX_SCAN_FOR_MODULES
.sp
Added in version 3.28.

.sp
\fBCXX_SCAN_FOR_MODULES\fP is a boolean specifying whether CMake will scan the
source for C++ module dependencies.  See also the
\fI\%CXX_SCAN_FOR_MODULES\fP for target\-wide settings.
.sp
When this property is set \fBON\fP, CMake will scan the source at build time and
add module dependency information to the compile line as necessary.  When this
property is set \fBOFF\fP, CMake will not scan the source at build time.  When
this property is unset, the \fI\%CXX_SCAN_FOR_MODULES\fP property is
consulted.
.sp
Note that scanning is only performed if C++20 or higher is enabled for the
target and the source uses the \fBCXX\fP language.  Scanning for modules in
sources belonging to file sets of type \fBCXX_MODULES\fP is always performed.
.SS EXTERNAL_OBJECT
.sp
If set to true then this is an object file.
.sp
If this property is set to \fBTrue\fP then the source file is really an
object file and should not be compiled.  It will still be linked into
the target though.
.SS Fortran_FORMAT
.sp
Set to \fBFIXED\fP or \fBFREE\fP to indicate the Fortran source layout.
.sp
This property tells CMake whether a given Fortran source file uses
fixed\-format or free\-format.  CMake will pass the corresponding format flag
to the compiler.  Consider using the target\-wide \fI\%Fortran_FORMAT\fP
property if all source files in a target share the same format.
.sp
\fBNOTE:\fP
.INDENT 0.0
.INDENT 3.5
For some compilers, \fBNAG\fP, \fBPGI\fP and \fBSolaris Studio\fP,
setting this to \fBOFF\fP will have no effect.
.UNINDENT
.UNINDENT
.SS Fortran_PREPROCESS
.sp
Added in version 3.18.

.sp
Control whether the Fortran source file should be unconditionally preprocessed.
.sp
If unset or empty, rely on the compiler to determine whether the file
should be preprocessed. If explicitly set to \fBOFF\fP then the file
does not need to be preprocessed. If explicitly set to \fBON\fP, then
the file does need to be preprocessed as part of the compilation step.
.sp
When using the \fI\%Ninja\fP generator, all source files are
first preprocessed in order to generate module dependency
information. Setting this property to \fBOFF\fP will make \fBNinja\fP
skip this step.
.sp
Consider using the target\-wide \fI\%Fortran_PREPROCESS\fP property
if all source files in a target need to be preprocessed.
.SS GENERATED
.sp
Is this source file generated as part of the build or CMake process.
.sp
Changed in version 3.20: Turning on the \fBGENERATED\fP source file property in one directory allows
the associated source file to be used across directories without the need
to manually setting that property for other directory scopes, too.
Additionally, it may now be set only to boolean values, and may not be
turned off once turned on.  See policy \fI\%CMP0118\fP\&.

.sp
Changed in version 3.30: Whether or not a source file is generated is an all\-or\-nothing global
property of the source.  Consequently, the \fBGENERATED\fP source file
property is now visible in all directories.  See policy \fI\%CMP0163\fP\&.

.sp
Tells the internal CMake engine that a source file is generated by an outside
process such as another build step, or the execution of CMake itself.
This information is then used to exempt the file from any existence or
validity checks.
.sp
Any file that is
.INDENT 0.0
.IP \(bu 2
created by the execution of commands such as
\fI\%add_custom_command()\fP which run during the build
.IP \(bu 2
listed as one of the \fBBYPRODUCTS\fP of an \fI\%add_custom_command()\fP
or \fI\%add_custom_target()\fP command, or
.IP \(bu 2
created by a CMake \fBAUTOGEN\fP operation such as \fI\%AUTOMOC\fP,
\fI\%AUTORCC\fP, or \fI\%AUTOUIC\fP
.UNINDENT
.sp
will be marked with the \fBGENERATED\fP property.
.sp
When a generated file created as the \fBOUTPUT\fP of an
\fI\%add_custom_command()\fP command is explicitly listed as a source file
for any target in the same directory scope (which usually means the same
\fBCMakeLists.txt\fP file), CMake will automatically create a dependency to
make sure the file is generated before building that target.
.sp
The \fI\%Makefile Generators\fP will remove \fBGENERATED\fP files during
\fBmake clean\fP\&.
.sp
Generated sources may be hidden in some IDE tools, while in others they might
be shown. For the special case of sources generated by CMake\(aqs \fI\%AUTOMOC\fP,
\fI\%AUTORCC\fP or \fI\%AUTOUIC\fP functionality, the
\fI\%AUTOGEN_SOURCE_GROUP\fP, \fI\%AUTOMOC_SOURCE_GROUP\fP,
\fI\%AUTORCC_SOURCE_GROUP\fP and \fI\%AUTOUIC_SOURCE_GROUP\fP target
properties may influence where the generated sources are grouped in the project\(aqs
file lists.
.SS HEADER_FILE_ONLY
.sp
Is this source file only a header file.
.sp
A property on a source file that indicates if the source file is a
header file with no associated implementation.  This is set
automatically based on the file extension and is used by CMake to
determine if certain dependency information should be computed.
.sp
By setting this property to \fBON\fP, you can disable compilation of
the given source file, even if it should be compiled because it is
part of the library\(aqs/executable\(aqs sources.
.sp
This is useful if you have some source files which you somehow
pre\-process, and then add these pre\-processed sources via
\fI\%add_library()\fP or \fI\%add_executable()\fP\&. Normally, in IDE,
there would be no reference of the original sources, only of these
pre\-processed sources. So by setting this property for all the original
source files to \fBON\fP, and then either calling \fI\%add_library()\fP
or \fI\%add_executable()\fP while passing both the pre\-processed
sources and the original sources, or by using \fI\%target_sources()\fP
to add original source files will do exactly what would one expect, i.e.
the original source files would be visible in IDE, and will not be built.
.SS INCLUDE_DIRECTORIES
.sp
Added in version 3.11.

.sp
List of preprocessor include file search directories.
.sp
This property holds a \fI\%semicolon\-separated list\fP of paths
and will be added to the list of include directories when this
source file builds. These directories will take precedence over directories
defined at target level except for \fI\%Xcode\fP generator due to technical
limitations.
.sp
Relative paths should not be added to this property directly.
.sp
Contents of \fBINCLUDE_DIRECTORIES\fP may use \(dqgenerator expressions\(dq with
the syntax \fB$<...>\fP\&.  See the \fI\%cmake\-generator\-expressions(7)\fP manual
for available expressions.  However, \fI\%Xcode\fP does not support
per\-config per\-source settings, so expressions that depend on the build
configuration are not allowed with that generator.
.SS KEEP_EXTENSION
.sp
Make the output file have the same extension as the source file.
.sp
If this property is set then the file extension of the output file
will be the same as that of the source file.  Normally the output file
extension is computed based on the language of the source file, for
example \fB\&.cxx\fP will go to a \fB\&.o\fP extension.
.SS LABELS
.sp
Specify a list of text labels associated with a source file.
.sp
This property has meaning only when the source file is listed in a
target whose \fBLABELS\fP property is also set.  No other semantics are
currently specified.
.SS LANGUAGE
.sp
Specify the programming language in which a source file is written.
.sp
A property that can be set to indicate what programming language the
source file is.  If it is not set the language is determined based on
the file extension.  Typical values are \fBCXX\fP (i.e.  C++), \fBC\fP,
\fBCSharp\fP, \fBCUDA\fP, \fBFortran\fP, \fBHIP\fP, \fBISPC\fP, and \fBASM\fP\&.  Setting
this property for a file means this file will be compiled, unless
\fI\%HEADER_FILE_ONLY\fP is set.
.sp
Changed in version 3.20: Setting this property causes the source file to be compiled as the
specified language, using explicit flags if possible.  Previously it
only caused the specified language\(aqs compiler to be used.
See policy \fI\%CMP0119\fP\&.

.SS LOCATION
.sp
The full path to a source file.
.sp
A read only property on a SOURCE FILE that contains the full path to
the source file.
.SS MACOSX_PACKAGE_LOCATION
.sp
Place a source file inside a Application Bundle
(\fI\%MACOSX_BUNDLE\fP), Core Foundation Bundle (\fI\%BUNDLE\fP),
or Framework Bundle (\fI\%FRAMEWORK\fP).  It is applicable for macOS
and iOS.
.sp
Executable targets with the \fI\%MACOSX_BUNDLE\fP property set are
built as macOS or iOS application bundles on Apple platforms.  Shared
library targets with the \fI\%FRAMEWORK\fP property set are built as
macOS or iOS frameworks on Apple platforms.  Module library targets with
the \fI\%BUNDLE\fP property set are built as macOS \fBCFBundle\fP bundles
on Apple platforms.  Source files listed in the target with this property
set will be copied to a directory inside the bundle or framework content
folder specified by the property value.  For macOS Application Bundles the
content folder is \fB<name>.app/Contents\fP\&.  For macOS Frameworks the
content folder is \fB<name>.framework/Versions/<version>\fP\&.  For macOS
CFBundles the content folder is \fB<name>.bundle/Contents\fP (unless the
extension is changed).  See the \fI\%PUBLIC_HEADER\fP,
\fI\%PRIVATE_HEADER\fP, and \fI\%RESOURCE\fP target properties for
specifying files meant for \fBHeaders\fP, \fBPrivateHeaders\fP, or
\fBResources\fP directories.
.sp
If the specified location is equal to \fBResources\fP, the resulting location
will be the same as if the \fI\%RESOURCE\fP property had been used. If
the specified location is a sub\-folder of \fBResources\fP, it will be placed
into the respective sub\-folder. Note: For iOS Apple uses a flat bundle layout
where no \fBResources\fP folder exist. Therefore CMake strips the \fBResources\fP
folder name from the specified location.
.sp
Added in version 4.1: \fBMACOSX_PACKAGE_LOCATION\fP may be set on a source directory
to copy its entire tree into the bundle.

.SS OBJECT_DEPENDS
.sp
Additional files on which a compiled object file depends.
.sp
Specifies a \fI\%semicolon\-separated list\fP of full\-paths to
files on which any object files compiled from this source file depend.
On \fI\%Makefile Generators\fP and the \fI\%Ninja\fP generator an
object file will be recompiled if any of the named files is newer than it.
\fI\%Visual Studio Generators\fP and the \fI\%Xcode\fP generator
cannot implement such compilation dependencies.
.sp
This property need not be used to specify the dependency of a source
file on a generated header file that it includes.  Although the
property was originally introduced for this purpose, it is no longer
necessary.  If the generated header file is created by a custom
command in the same target as the source file, the automatic
dependency scanning process will recognize the dependency.  If the
generated header file is created by another target, an inter\-target
dependency should be created with the \fI\%add_dependencies()\fP
command (if one does not already exist due to linking relationships).
.SS OBJECT_OUTPUTS
.sp
Additional outputs for a \fI\%Ninja\fP or \fI\%Makefile Generators\fP rule.
.sp
Additional outputs created by compilation of this source file.  If any
of these outputs is missing the object will be recompiled.  This is
supported only on the \fI\%Ninja\fP and \fI\%Makefile Generators\fP
and will be ignored on other generators.
.sp
This property supports
\fI\%generator expressions\fP\&.
.SS SKIP_AUTOGEN
.sp
Added in version 3.8.

.sp
Exclude the source file from \fI\%AUTOMOC\fP, \fI\%AUTOUIC\fP and
\fI\%AUTORCC\fP processing (for Qt projects).
.sp
For finer exclusion control see \fI\%SKIP_AUTOMOC\fP,
\fI\%SKIP_AUTOUIC\fP and \fI\%SKIP_AUTORCC\fP\&.
.SS EXAMPLE
.INDENT 0.0
.INDENT 3.5
.sp
.EX
# ...
set_property(SOURCE file.h PROPERTY SKIP_AUTOGEN ON)
# ...
.EE
.UNINDENT
.UNINDENT
.SS SKIP_AUTOMOC
.sp
Added in version 3.8.

.sp
Exclude the source file from \fI\%AUTOMOC\fP processing (for Qt projects).
.sp
For broader exclusion control see \fI\%SKIP_AUTOGEN\fP\&.
.SS EXAMPLE
.INDENT 0.0
.INDENT 3.5
.sp
.EX
# ...
set_property(SOURCE file.h PROPERTY SKIP_AUTOMOC ON)
# ...
.EE
.UNINDENT
.UNINDENT
.SS SKIP_AUTORCC
.sp
Added in version 3.8.

.sp
Exclude the source file from \fI\%AUTORCC\fP processing (for Qt projects).
.sp
For broader exclusion control see \fI\%SKIP_AUTOGEN\fP\&.
.SS EXAMPLE
.INDENT 0.0
.INDENT 3.5
.sp
.EX
# ...
set_property(SOURCE file.qrc PROPERTY SKIP_AUTORCC ON)
# ...
.EE
.UNINDENT
.UNINDENT
.SS SKIP_AUTOUIC
.sp
Added in version 3.8.

.sp
Exclude the source file from \fI\%AUTOUIC\fP processing (for Qt projects).
.sp
\fBSKIP_AUTOUIC\fP can be set on C++ header and source files and on
\fB\&.ui\fP files.
.sp
For broader exclusion control see \fI\%SKIP_AUTOGEN\fP\&.
.SS EXAMPLE
.INDENT 0.0
.INDENT 3.5
.sp
.EX
# ...
set_property(SOURCE file.h PROPERTY SKIP_AUTOUIC ON)
set_property(SOURCE file.cpp PROPERTY SKIP_AUTOUIC ON)
set_property(SOURCE widget.ui PROPERTY SKIP_AUTOUIC ON)
# ...
.EE
.UNINDENT
.UNINDENT
.SS SKIP_LINTING
.sp
Added in version 3.27.

.sp
This property allows you to exclude a specific source file
from the linting process. The linting process involves running
tools such as \fI\%<LANG>_CPPLINT\fP, \fI\%<LANG>_CLANG_TIDY\fP,
\fI\%<LANG>_CPPCHECK\fP, \fI\%<LANG>_ICSTAT\fP and
\fI\%<LANG>_INCLUDE_WHAT_YOU_USE\fP on the source files, as well
as compiling header files as part of \fI\%VERIFY_INTERFACE_HEADER_SETS\fP\&.
By setting \fBSKIP_LINTING\fP on a source file, the mentioned linting tools
will not be executed for that particular file.
.SS Example
.sp
Consider a C++ project that includes multiple source files,
such as \fBmain.cpp\fP, \fBthings.cpp\fP, and \fBgeneratedBindings.cpp\fP\&.
In this example, you want to exclude the \fBgeneratedBindings.cpp\fP
file from the linting process. To achieve this, you can utilize
the \fBSKIP_LINTING\fP property with the \fI\%set_source_files_properties()\fP
command as shown below:
.INDENT 0.0
.INDENT 3.5
.sp
.EX
add_executable(MyApp main.cpp things.cpp generatedBindings.cpp)

set_source_files_properties(generatedBindings.cpp PROPERTIES
    SKIP_LINTING ON
)
.EE
.UNINDENT
.UNINDENT
.sp
In the provided code snippet, the \fBSKIP_LINTING\fP property is set to true
for the \fBgeneratedBindings.cpp\fP source file. As a result, when the linting
tools specified by \fI\%<LANG>_CPPLINT\fP, \fI\%<LANG>_CLANG_TIDY\fP,
\fI\%<LANG>_CPPCHECK\fP, \fI\%<LANG>_ICSTAT\fP or
\fI\%<LANG>_INCLUDE_WHAT_YOU_USE\fP are executed, they will skip analyzing
the \fBgeneratedBindings.cpp\fP file.
.sp
By using the \fBSKIP_LINTING\fP property, you can selectively exclude specific
source files from the linting process. This allows you to focus the
linting tools on the relevant parts of your project, enhancing the efficiency
and effectiveness of the linting workflow.
.SS SKIP_PRECOMPILE_HEADERS
.sp
Added in version 3.16.

.sp
Is this source file skipped by \fI\%PRECOMPILE_HEADERS\fP feature.
.sp
This property helps with build problems that one would run into
when using the \fI\%PRECOMPILE_HEADERS\fP feature.
.sp
One example would be the usage of Objective\-C (\fB*.m\fP) files, and
Objective\-C++ (\fB*.mm\fP) files, which lead to compilation failure
because they are treated (in case of Ninja / Makefile generator)
as C, and CXX respectively. The precompile headers are not
compatible between languages.
.SS SKIP_UNITY_BUILD_INCLUSION
.sp
Added in version 3.16.

.sp
Setting this property to true ensures the source file will be skipped by
unity builds when its associated target has its \fI\%UNITY_BUILD\fP
property set to true.  The source file will instead be compiled on its own
in the same way as it would with unity builds disabled.
.sp
This property helps with \(dqODR (One definition rule)\(dq problems where combining
a particular source file with others might lead to build errors or other
unintended side effects.
.sp
Note that sources which are scanned for C++ modules (see
\fI\%cmake\-cxxmodules(7)\fP) are not eligible for unity build inclusion and
will automatically be excluded.
.SS Swift_DEPENDENCIES_FILE
.sp
Added in version 3.15.

.sp
This property sets the path for the Swift dependency file (swiftdeps) for the
source.  If one is not specified, it will default to \fB<OBJECT>.swiftdeps\fP\&.
.SS Swift_DIAGNOSTICS_FILE
.sp
Added in version 3.15.

.sp
This property controls where the Swift diagnostics are serialized.
.SS SYMBOLIC
.sp
Is this just a name for a rule.
.sp
If \fBSYMBOLIC\fP (boolean) is set to \fBTrue\fP the build system will be informed
that the source file is not actually created on disk but instead used
as a symbolic name for a build rule.
.SS UNITY_GROUP
.sp
Added in version 3.18.

.sp
This property controls which \fIbucket\fP the source will be part of when
the \fI\%UNITY_BUILD_MODE\fP is set to \fBGROUP\fP\&.
.SS VS_COPY_TO_OUT_DIR
.sp
Added in version 3.8.

.sp
Sets the \fB<CopyToOutputDirectory>\fP tag for a source file in a
Visual Studio project file. Valid values are \fBNever\fP, \fBAlways\fP
and \fBPreserveNewest\fP\&.
.SS VS_CSHARP_<tagname>
.sp
Added in version 3.8.

.sp
Visual Studio and CSharp source\-file\-specific configuration.
.sp
Tell the \fI\%Visual Studio Generators\fP
to set the source file tag \fB<tagname>\fP
to a given value in the generated Visual Studio CSharp
project. Ignored on other generators and languages. This property
can be used to define dependencies between source files or set any
other Visual Studio specific parameters.
.SS Examples
.sp
Example usage:
.INDENT 0.0
.INDENT 3.5
.sp
.EX
set_source_files_properties(<filename>
         PROPERTIES
         VS_CSHARP_DependentUpon <other file>
         VS_CSHARP_SubType \(dqForm\(dq)
.EE
.UNINDENT
.UNINDENT
.SS See Also
.INDENT 0.0
.IP \(bu 2
The \fI\%CSharpUtilities\fP module for configuring CSharp/.NET targets.
.UNINDENT
.SS VS_CUSTOM_COMMAND_DISABLE_PARALLEL_BUILD
.sp
Added in version 4.0.

.sp
A boolean property that disables parallel building for the source file in
Visual Studio if it is built via \fI\%add_custom_command()\fP and is the
\fBMAIN_DEPENDENCY\fP input for the custom command.
See policy \fI\%CMP0147\fP\&.
.SS VS_DEPLOYMENT_CONTENT
.sp
Added in version 3.1.

.sp
Mark a source file as content for deployment with a Windows Phone or
Windows Store application when built with a
\fI\%Visual Studio Generators\fP\&.
The value must evaluate to either \fB1\fP or \fB0\fP and may use
\fI\%generator expressions\fP
to make the choice based on the build configuration.
The \fB\&.vcxproj\fP file entry for the source file will be
marked either \fBDeploymentContent\fP or \fBExcludedFromBuild\fP
for values \fB1\fP and \fB0\fP, respectively.
.SS VS_DEPLOYMENT_LOCATION
.sp
Added in version 3.1.

.sp
Specifies the deployment location for a content source file with a Windows
Phone or Windows Store application when built
with a \fI\%Visual Studio generators\fP\&.
This property is only applicable when using \fI\%VS_DEPLOYMENT_CONTENT\fP\&.
The value represent the path relative to the app package and applies to all
configurations.
.SS VS_INCLUDE_IN_VSIX
.sp
Added in version 3.8.

.sp
Boolean property to specify if the file should be included within a
VSIX (Visual Studio Integration Extension) extension package.
This is needed for development of Visual Studio extensions.
.SS VS_RESOURCE_GENERATOR
.sp
Added in version 3.8.

.sp
This property allows to specify the resource generator to be used
on this file. It defaults to \fBPublicResXFileCodeGenerator\fP if
not set.
.sp
This property only applies to C# projects.
.SS VS_SETTINGS
.sp
Added in version 3.18.

.sp
Add arbitrary MSBuild item metadata to a file.
.sp
This property accepts a list of \fBKey=Value\fP pairs. The Visual Studio
generator will add these key\-value pairs as item metadata to the file.
\fI\%Generator expressions\fP are supported.
.sp
For example:
.INDENT 0.0
.INDENT 3.5
.sp
.EX
set_property(SOURCE file.hlsl PROPERTY VS_SETTINGS \(dqKey=Value\(dq \(dqKey2=Value2\(dq)
.EE
.UNINDENT
.UNINDENT
.sp
will set the \fBfile.hlsl\fP item metadata as follows:
.INDENT 0.0
.INDENT 3.5
.sp
.EX
<FXCompile Include=\(dqsource_path\efile.hlsl\(dq>
  <Key>Value</Key>
  <Key2>Value2</Key2>
</FXCompile>
.EE
.UNINDENT
.UNINDENT
.sp
Together with \fI\%VS_TOOL_OVERRIDE\fP, this property can be used to
configure items for custom MSBuild tasks.
.sp
Adding the metadata \fBExcludedFromBuild=true\fP will exclude the file from
the build.
.sp
Changed in version 3.22: This property is honored for all source file types.
Previously, it only worked for source types unknown to CMake.

.SS VS_SHADER_DISABLE_OPTIMIZATIONS
.sp
Added in version 3.11.

.sp
Disable compiler optimizations for an \fB\&.hlsl\fP source file.  This adds the
\fB\-Od\fP flag to the command line for the FxCompiler tool.  Specify the value
\fBtrue\fP for this property to disable compiler optimizations.
.SS VS_SHADER_ENABLE_DEBUG
.sp
Added in version 3.11.

.sp
Enable debugging information for an \fB\&.hlsl\fP source file.  This adds the
\fB\-Zi\fP flag to the command line for the FxCompiler tool.  Specify the value
\fBtrue\fP to generate debugging information for the compiled shader.
.SS VS_SHADER_ENTRYPOINT
.sp
Added in version 3.1.

.sp
Specifies the name of the entry point for the shader of a \fB\&.hlsl\fP source
file.
.SS VS_SHADER_FLAGS
.sp
Added in version 3.2.

.sp
Set additional Visual Studio shader flags of a \fB\&.hlsl\fP source file.
.SS VS_SHADER_MODEL
.sp
Added in version 3.1.

.sp
Specifies the shader model of a \fB\&.hlsl\fP source file. Some shader types can
only be used with recent shader models
.SS VS_SHADER_OBJECT_FILE_NAME
.sp
Added in version 3.12.

.sp
Specifies a file name for the compiled shader object file for an \fB\&.hlsl\fP
source file.  This adds the \fB\-Fo\fP flag to the command line for the FxCompiler
tool.
.SS VS_SHADER_OUTPUT_HEADER_FILE
.sp
Added in version 3.10.

.sp
Set filename for output header file containing object code of a \fB\&.hlsl\fP
source file.
.SS VS_SHADER_TYPE
.sp
Added in version 3.1.

.sp
Set the Visual Studio shader type of a \fB\&.hlsl\fP source file.
.SS VS_SHADER_VARIABLE_NAME
.sp
Added in version 3.10.

.sp
Set name of variable in header file containing object code of a \fB\&.hlsl\fP
source file.
.SS VS_TOOL_OVERRIDE
.sp
Added in version 3.7.

.sp
Override the MSBuild item type of a source file in a Visual Studio project.
.sp
Together with \fI\%VS_SETTINGS\fP, this property can be used to configure
items for custom MSBuild tasks.
.sp
Setting the item type to \fBNone\fP will exclude the file from the build.
.sp
Changed in version 3.31: This property is honored for all source file types.
Previously, it only worked for source types unknown to CMake.

.SS VS_XAML_TYPE
.sp
Added in version 3.3.

.sp
Mark a Extensible Application Markup Language (XAML) source file
as a different type than the default \fBPage\fP\&.
The most common usage would be to set the default \fBApp.xaml\fP file as
\fBApplicationDefinition\fP\&.
.SS WRAP_EXCLUDE
.sp
Exclude this source file from any code wrapping techniques.
.sp
Some packages can wrap source files into alternate languages to
provide additional functionality.
.sp
For example, C++ code can be wrapped into Java or Python, using SWIG.
If \fBWRAP_EXCLUDE\fP is set to \fBTrue\fP, that indicates that this
source file should not be wrapped.
.SS XCODE_EXPLICIT_FILE_TYPE
.sp
Added in version 3.1.

.sp
Set the \fI\%Xcode\fP \fBexplicitFileType\fP attribute on its reference to a
source file.  CMake computes a default based on file extension but
can be told explicitly with this property.
.sp
See also \fI\%XCODE_LAST_KNOWN_FILE_TYPE\fP\&.
.SS XCODE_FILE_ATTRIBUTES
.sp
Added in version 3.7.

.sp
Add values to the \fI\%Xcode\fP \fBATTRIBUTES\fP setting on its reference to a
source file.  Among other things, this can be used to set the role on
a \fB\&.mig\fP file:
.INDENT 0.0
.INDENT 3.5
.sp
.EX
set_source_files_properties(defs.mig
    PROPERTIES
        XCODE_FILE_ATTRIBUTES \(dqClient;Server\(dq
)
.EE
.UNINDENT
.UNINDENT
.SS XCODE_LAST_KNOWN_FILE_TYPE
.sp
Added in version 3.1.

.sp
Set the \fI\%Xcode\fP \fBlastKnownFileType\fP attribute on its reference to
a source file.  CMake computes a default based on file extension but
can be told explicitly with this property.
.sp
See also \fI\%XCODE_EXPLICIT_FILE_TYPE\fP, which is preferred
over this property if set.
.SH PROPERTIES ON CACHE ENTRIES
.SS ADVANCED
.sp
True if entry should be hidden by default in GUIs.
.sp
This is a boolean value indicating whether the entry is considered
interesting only for advanced configuration.  The \fI\%mark_as_advanced()\fP
command modifies this property.
.SS HELPSTRING
.sp
Help associated with entry in GUIs.
.sp
This string summarizes the purpose of an entry to help users set it
through a CMake GUI.
.SS MODIFIED
.sp
Internal management property.  Do not set or get.
.sp
This is an internal cache entry property managed by CMake to track
interactive user modification of entries.  Ignore it.
.SS STRINGS
.sp
Enumerate possible \fBSTRING\fP entry values for GUI selection.
.sp
For cache entries with type \fBSTRING\fP, this enumerates a set of values.
CMake GUIs may use this to provide a selection widget instead of a
generic string entry field.  This is for convenience only.  CMake does
not enforce that the value matches one of those listed.
.SS TYPE
.sp
Widget type for entry in GUIs.
.sp
Cache entry values are always strings, but CMake GUIs present widgets
to help users set values.  The GUIs use this property as a hint to
determine the widget type.  Valid \fBTYPE\fP values are:
.TS
box center;
l|l.
T{
\fBBOOL\fP
T}	T{
Boolean ON/OFF value.
T}
_
T{
\fBPATH\fP
T}	T{
Path to a directory.
T}
_
T{
\fBFILEPATH\fP
T}	T{
Path to a file.
T}
_
T{
\fBSTRING\fP
T}	T{
Generic string value.
T}
_
T{
\fBINTERNAL\fP
T}	T{
Do not present in GUI at all.
T}
_
T{
\fBSTATIC\fP
T}	T{
Value managed by CMake, do not change.
T}
_
T{
\fBUNINITIALIZED\fP
T}	T{
Type not yet specified.
T}
.TE
.sp
Generally the \fBTYPE\fP of a cache entry should be set by the command which
creates it (\fI\%set()\fP, \fI\%option()\fP, \fI\%find_library()\fP, etc.).
.SS VALUE
.sp
Value of a cache entry.
.sp
This property maps to the actual value of a cache entry.  Setting this
property always sets the value without checking, so use with care.
.SH PROPERTIES ON INSTALLED FILES
.SS CPACK_DESKTOP_SHORTCUTS
.sp
Added in version 3.3.

.sp
Species a list of shortcut names that should be created on the \fBDesktop\fP
for this file.
.sp
The property is currently only supported by the \fI\%CPack WIX Generator\fP\&.
.SS CPACK_NEVER_OVERWRITE
.sp
Added in version 3.1.

.sp
Request that this file not be overwritten on install or reinstall.
.sp
The property is currently only supported by the \fI\%CPack WIX Generator\fP\&.
.SS CPACK_PERMANENT
.sp
Added in version 3.1.

.sp
Request that this file not be removed on uninstall.
.sp
The property is currently only supported by the \fI\%CPack WIX Generator\fP\&.
.SS CPACK_START_MENU_SHORTCUTS
.sp
Added in version 3.3.

.sp
Species a list of shortcut names that should be created in the \fBStart Menu\fP
for this file.
.sp
The property is currently only supported by the \fI\%CPack WIX Generator\fP\&.
.SS CPACK_STARTUP_SHORTCUTS
.sp
Added in version 3.3.

.sp
Species a list of shortcut names that should be created in the \fBStartup\fP folder
for this file.
.sp
The property is currently only supported by the \fI\%CPack WIX Generator\fP\&.
.SS CPACK_WIX_ACL
.sp
Added in version 3.1.

.sp
Specifies access permissions for files or directories
installed by a WiX installer.
.sp
The property can contain multiple list entries,
each of which has to match the following format.
.INDENT 0.0
.INDENT 3.5
.sp
.EX
<user>[@<domain>]=<permission>[,<permission>]
.EE
.UNINDENT
.UNINDENT
.sp
\fB<user>\fP and \fB<domain>\fP specify the windows user and domain for which the
\fB<Permission>\fP element should be generated.
.sp
\fB<permission>\fP is any of the YesNoType attributes listed at:
\X'tty: link https://docs.firegiant.com/wix3/xsd/wix/permission/'\fI\%https://docs.firegiant.com/wix3/xsd/wix/permission/\fP\X'tty: link'
.sp
The property is currently only supported by the \fI\%CPack WIX Generator\fP\&.
.SH DEPRECATED PROPERTIES ON DIRECTORIES
.SS ADDITIONAL_MAKE_CLEAN_FILES
.sp
Deprecated since version 3.15: Use \fI\%ADDITIONAL_CLEAN_FILES\fP instead.

.sp
Additional files to remove during the clean stage.
.sp
A \fI\%;\-list\fP of files that will be removed as a
part of the \fBmake clean\fP target.
.sp
Arguments to \fBADDITIONAL_MAKE_CLEAN_FILES\fP may use
\fI\%generator expressions\fP\&.
.sp
This property only works for the Makefile generators.
It is ignored on other generators.
.SS COMPILE_DEFINITIONS_<CONFIG>
.sp
Ignored.  See CMake Policy \fI\%CMP0043\fP\&.
.sp
Per\-configuration preprocessor definitions in a directory.
.sp
This is the configuration\-specific version of \fI\%COMPILE_DEFINITIONS\fP
where \fB<CONFIG>\fP is an upper\-case name (ex. \fBCOMPILE_DEFINITIONS_DEBUG\fP).
.sp
This property will be initialized in each directory by its value in
the directory\(aqs parent.
.sp
Contents of \fBCOMPILE_DEFINITIONS_<CONFIG>\fP may use \(dqgenerator expressions\(dq
with the syntax \fB$<...>\fP\&.  See the \fI\%cmake\-generator\-expressions(7)\fP
manual for available expressions.  See the \fI\%cmake\-buildsystem(7)\fP
manual for more on defining buildsystem properties.
.sp
Generator expressions should be preferred instead of setting this property.
.SS INTERPROCEDURAL_OPTIMIZATION
.sp
This directory property does not exist anymore.
.sp
See the target property \fI\%INTERPROCEDURAL_OPTIMIZATION\fP instead.
.SS INTERPROCEDURAL_OPTIMIZATION_<CONFIG>
.sp
This directory property does not exist anymore.
.sp
See the target property \fI\%INTERPROCEDURAL_OPTIMIZATION_<CONFIG>\fP instead.
.SS TEST_INCLUDE_FILE
.sp
Deprecated since version 3.10: Use the \fI\%TEST_INCLUDE_FILES\fP directory property instead, which
supports specifying multiple files.

.sp
The \fBTEST_INCLUDE_FILE\fP directory property specifies a CMake script that is
included and processed when \fBctest\fP is run on the directory.
.sp
If both the \fBTEST_INCLUDE_FILE\fP and \fI\%TEST_INCLUDE_FILES\fP directory
properties are set, the script specified in \fBTEST_INCLUDE_FILE\fP is included
first, followed by the scripts listed in \fBTEST_INCLUDE_FILES\fP\&.
.SH DEPRECATED PROPERTIES ON TARGETS
.SS COMPILE_DEFINITIONS_<CONFIG>
.sp
Ignored.  See CMake Policy \fI\%CMP0043\fP\&.
.sp
Per\-configuration preprocessor definitions on a target.
.sp
This is the configuration\-specific version of \fI\%COMPILE_DEFINITIONS\fP
where \fB<CONFIG>\fP is an upper\-case name (ex. \fBCOMPILE_DEFINITIONS_DEBUG\fP).
.sp
Contents of \fBCOMPILE_DEFINITIONS_<CONFIG>\fP may use \(dqgenerator expressions\(dq
with the syntax \fB$<...>\fP\&.  See the \fI\%cmake\-generator\-expressions(7)\fP
manual for available expressions.  See the \fI\%cmake\-buildsystem(7)\fP
manual for more on defining buildsystem properties.
.sp
Generator expressions should be preferred instead of setting this property.
.SS Fortran_BUILDING_INSTRINSIC_MODULES
.sp
Deprecated since version 4.0: Please use the \fI\%Fortran_BUILDING_INTRINSIC_MODULES\fP instead.

.sp
Added in version 3.22.

.sp
A misspelled variant of the \fI\%Fortran_BUILDING_INTRINSIC_MODULES\fP
target property.
.SS IMPORTED_NO_SYSTEM
.sp
Added in version 3.23.

.sp
Deprecated since version 3.25: \fBIMPORTED_NO_SYSTEM\fP is deprecated. Please use the following alternatives
instead:
.INDENT 0.0
.IP \(bu 2
Set \fI\%SYSTEM\fP to false if you don\(aqt want a target\(aqs include
directories to be treated as system directories when compiling consumers.
.IP \(bu 2
Set \fI\%EXPORT_NO_SYSTEM\fP to true if you don\(aqt want the include
directories of the imported target generated by \fI\%install(EXPORT)\fP
and \fI\%export()\fP commands to be treated as system directories when
compiling consumers.
.UNINDENT

.sp
Setting \fBIMPORTED_NO_SYSTEM\fP to true on an
\fI\%imported target\fP specifies that it is not a
system target.  This has the following effects:
.INDENT 0.0
.IP \(bu 2
Entries of \fI\%INTERFACE_INCLUDE_DIRECTORIES\fP are not treated
as system include directories when compiling consumers (regardless of
the value of the consumed target\(aqs \fI\%SYSTEM\fP property), as they
would be by default.   Entries of
\fI\%INTERFACE_SYSTEM_INCLUDE_DIRECTORIES\fP are not affected,
and will always be treated as system include directories.
.IP \(bu 2
On Apple platforms, when the target is a framework, it will not be treated as
system.
.UNINDENT
.sp
This property can also be enabled on a non\-imported target.  Doing so does
not affect the build system, but does tell the \fI\%install(EXPORT)\fP and
\fI\%export()\fP commands to enable it on the imported targets they generate.
.sp
See the \fI\%NO_SYSTEM_FROM_IMPORTED\fP target property to set this
behavior on the target \fIconsuming\fP the include directories rather than
the one \fIproviding\fP them.
.SS IOS_INSTALL_COMBINED
.sp
Added in version 3.5.

.sp
Deprecated since version 3.28: \fI\%IOS_INSTALL_COMBINED\fP was designed to make universal binaries
containing iOS/arm* device code paired with iOS Simulator/x86_64 code
(or similar for other Apple embedded platforms). Universal binaries can only
differentiate code based on CPU type, so this only made sense before the
days of arm64 macOS machines (i.e. iOS Simulator/arm64). Apple now
recommends xcframeworks, which contain multiple binaries for different
platforms, for this use case.

.sp
Build a combined (device and simulator) target when installing.
.sp
When this property is set to false, which is the default, then it will
either be built with the device SDK or the simulator SDK depending on the SDK
set. But if this property is set to true then the target will at install time
also be built for the other SDK and combined into one library.
.sp
\fBNOTE:\fP
.INDENT 0.0
.INDENT 3.5
If a selected architecture is available for both device SDK and simulator
SDK it will be built for the SDK selected by \fI\%CMAKE_OSX_SYSROOT\fP
and removed from the other SDK.
.UNINDENT
.UNINDENT
.sp
This feature requires at least Xcode version 6.
.SS POST_INSTALL_SCRIPT
.sp
Deprecated install support.
.sp
The \fI\%PRE_INSTALL_SCRIPT\fP and \fBPOST_INSTALL_SCRIPT\fP properties are
the old way to specify CMake scripts to run before and after installing a
target.  They are used only when the old \fBINSTALL_TARGETS\fP command is
used to install the target.  Use the \fI\%install()\fP command instead.
.SS PRE_INSTALL_SCRIPT
.sp
Deprecated install support.
.sp
The \fBPRE_INSTALL_SCRIPT\fP and \fI\%POST_INSTALL_SCRIPT\fP properties are
the old way to specify CMake scripts to run before and after installing a
target.  They are used only when the old \fBINSTALL_TARGETS\fP command is
used to install the target.  Use the \fI\%install()\fP command instead.
.SS VS_WINRT_EXTENSIONS
.sp
Deprecated.  Use \fI\%VS_WINRT_COMPONENT\fP instead.
This property was an experimental partial implementation of that one.
.SH DEPRECATED PROPERTIES ON SOURCE FILES
.SS COMPILE_DEFINITIONS_<CONFIG>
.sp
Deprecated since version 3.0: Prefer the \fI\%COMPILE_DEFINITIONS\fP source\-file property with
\fI\%generator expressions\fP\&.

.sp
Per\-configuration preprocessor definitions on a source file.
.sp
This is the configuration\-specific version of \fI\%COMPILE_DEFINITIONS\fP\&.
.sp
Note that \fI\%Xcode\fP does not support per\-configuration source
file flags so this property will be ignored by the \fI\%Xcode\fP generator.
.SH COPYRIGHT
2000-2025 Kitware, Inc. and Contributors
.\" Generated by docutils manpage writer.
.
